W/o this fix, rabbitmqctl sometimes may hang failing
many commands. This is a problem as it brings the rabbit node
to unresponsive and broken state. This also may affect
entire cluster operations, for example, when the failed command is
the forget_cluster_node.
The solution is to check for the cases when the command rabbitmqctl
list_channels timed out and killed or termintated with exit codes
137 or 124 and return generic error.
There is also related confusing error message "get_status() returns generic
error" may be logged when the rabbit node is running out of the cluster
and fixed as well.
Reviewed: https:/ /review. openstack. org/186002 /git.openstack. org/cgit/ stackforge/ fuel-library/ commit/ ?id=e8e777a55b6 d31e197c97cc638 0c2c0e49927b0a
Committed: https:/
Submitter: Jenkins
Branch: master
commit e8e777a55b6d31e 197c97cc6380c2c 0e49927b0a
Author: Bogdan Dobrelya <email address hidden>
Date: Wed May 27 15:47:42 2015 +0200
Check if the rabbitmqctl command is responding
W/o this fix, rabbitmqctl sometimes may hang failing cluster_ node.
many commands. This is a problem as it brings the rabbit node
to unresponsive and broken state. This also may affect
entire cluster operations, for example, when the failed command is
the forget_
The solution is to check for the cases when the command rabbitmqctl
list_channels timed out and killed or termintated with exit codes
137 or 124 and return generic error.
There is also related confusing error message "get_status() returns generic
error" may be logged when the rabbit node is running out of the cluster
and fixed as well.
Closes-bug: #1459173
Change-Id: Ia52fc5f2ab7adb 36252a7194f9209 ab87ce487de
Signed-off-by: Bogdan Dobrelya <email address hidden>