A queue with a name like "t_0" subscribed to _$HUBALL on my secondary hub is backing up and the messages are not draining quickly enough.
DX UIM 23.4.5
discovery_server 23.4.5
large environment/slow network
On a slow network or one with high response times between hubs, this queue can get backed up temporarily. It is not generally a problem and can be ignored as long as the messages are still draining.
If they have stopped draining, you may need to right-click the queue in the hub GUI and select "Empty" to clear the backlog.
In DX UIM 23.4.6 (CU6) there will be a way to disable the creation of these queues.
What is the queue with Subject _$HUBALL for?