swapping clustered qpid broker becomes irresponsive
Issue
When all clustered brokers within the cluster are swapping (on purpose, due to the amount of messages sent to them), one of the broker stops responding. Its CPU usage stalls at 100% forever. All other brokers are fine. What happens to the stalled broker?
Environment
- MRG Messaging 2.0, 2.1, 2.2 and 2.3
- qpid clustering used
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
