Reference: Clustered Grouping Best Practices

WARNING - TOPIC NOT WRITTEN - TOPIC ID: 700

This topic has not yet been written. The content below is from the topic description.
28.5.1. Clustered Grouping Best Practices Some best practices should be followed when using clustered grouping: Make sure your consumers are distributed evenly across the different nodes if possible. This is only an issue if you are creating and closing consumers regularly. Since messages are always routed to the same queue once pinned, removing a consumer from this queue may leave it with no consumers meaning the queue will just keep receiving the messages. Avoid closing consumers or make sure that you always have plenty of consumers, i.e., if you have 3 nodes have 3 consumers. Use durable queues if possible. If queues are removed once a group is bound to it, then it is possible that other nodes may still try to route messages to it. This can be avoided by making sure that the queue is deleted by the session that is sending the messages. This means that when the next message is sent it is sent to the node where the queue was deleted meaning a new proposal can succesfully take place. Alternatively you could just start using a different group id. Always make sure that the node that has the Local Grouping Handler is replicated. These means that on failover grouping will still occur.