c882b7f9cf
Upstream PR: https://github.com/rabbitmq/rabbitmq-server/pull/563 Currently time-out when running 'rabbitmqctl list_channels' is treated as a sign that current node is unhealthy. But it could not be the case, as the hanging channel could be actually on some other node. Given that currently we have seen more than one bug related to 'list_channels', it makes sense to improve diagnostics here. This patch doesn't change any behaviour, only improves logging after time-out happens. If time-outs continue to occur (even with latest rabbitmq versions or with backported fixes), we could switch to this improved list_channels and kill rabbitmq only if stuck channels are located on current node. But I hope that all related rabbitmq bugs were already closed. Change-Id: I4746d3a4e85dc2a51af581034ae09a1cf0eefce2 Partial-Bug: #1515223 Partial-Bug: #1513511 |
||
---|---|---|
.. | ||
ocf | ||
tools |