)]}'
{"pages/operations/troubleshoot/9140-amqp.rst":[{"author":{"_account_id":6926,"name":"Bogdan Dobrelya","email":"bdobreli@redhat.com","username":"bogdando"},"change_message_id":"ef695e8d6dd296797effb36e4a1fa2865fa8cbf7","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Normally, failures of the RabbitMQ multistate resource are automatically"},{"line_number":20,"context_line":"fixed by Corosync and Pacemaker. But if a failure cannot be automatically fixed"},{"line_number":21,"context_line":"for some reason, the master_p_rabbitmq-server resource status will be reported as \"bad\"."},{"line_number":22,"context_line":"The status is reported as \"good\" when there exists a single master for the"},{"line_number":23,"context_line":"master_p_rabbitmq-server and the rest of the resource instances are reported"},{"line_number":24,"context_line":"as slaves. Note, that the command ``pcs status`` issued on all controllers"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7a016987_af47074a","line":21,"updated":"2015-05-18 13:19:44.000000000","message":"these \"bad\" and \"good\" are rather a description than the actual statuses. After rephrase, it seems as there are some \"bad\" and \"good\" words must be reported, but there are no such ones... Please change to consider/considred as","commit_id":"607b08b7a29c5e368ee8f9632647c4d72242e196"},{"author":{"_account_id":6926,"name":"Bogdan Dobrelya","email":"bdobreli@redhat.com","username":"bogdando"},"change_message_id":"ef695e8d6dd296797effb36e4a1fa2865fa8cbf7","unresolved":false,"context_lines":[{"line_number":19,"context_line":"Normally, failures of the RabbitMQ multistate resource are automatically"},{"line_number":20,"context_line":"fixed by Corosync and Pacemaker. But if a failure cannot be automatically fixed"},{"line_number":21,"context_line":"for some reason, the master_p_rabbitmq-server resource status will be reported as \"bad\"."},{"line_number":22,"context_line":"The status is reported as \"good\" when there exists a single master for the"},{"line_number":23,"context_line":"master_p_rabbitmq-server and the rest of the resource instances are reported"},{"line_number":24,"context_line":"as slaves. Note, that the command ``pcs status`` issued on all controllers"},{"line_number":25,"context_line":"should be enough to gather all the required information, see :ref:`crm-ops`."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7a016987_cf6363db","line":22,"updated":"2015-05-18 13:19:44.000000000","message":"ditto","commit_id":"607b08b7a29c5e368ee8f9632647c4d72242e196"},{"author":{"_account_id":3012,"name":"Dina Belova","email":"dbelova@mirantis.com","username":"dbelova"},"change_message_id":"f5665cff47b0eb3bcf6855f8dcefbcd61424a978","unresolved":false,"context_lines":[{"line_number":5,"context_line":"How To Troubleshoot AMQP issues"},{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"AMQP is the heart of OpenStack. If something gets wrong with"},{"line_number":9,"context_line":"the messaging layer, normally an OpenStack application can tolerate"},{"line_number":10,"context_line":"this by issuing reconnects, reporting some requests as failed or"},{"line_number":11,"context_line":"retrying them. While this depends on the particular application"}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a016987_24888ec4","line":8,"range":{"start_line":8,"start_character":45,"end_line":8,"end_character":49},"updated":"2015-05-21 16:41:28.000000000","message":"gets -\u003e goes?","commit_id":"476483fdae835495dbe1bb4f525ca624915069b0"},{"author":{"_account_id":3012,"name":"Dina Belova","email":"dbelova@mirantis.com","username":"dbelova"},"change_message_id":"f5665cff47b0eb3bcf6855f8dcefbcd61424a978","unresolved":false,"context_lines":[{"line_number":17,"context_line":"-----------------------------------------------------------"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Normally, failures of the RabbitMQ multistate resource are automatically"},{"line_number":20,"context_line":"fixed by Corosync and Pacemaker. But if a failure cannot be automatically fixed"},{"line_number":21,"context_line":"for some reason, the master_p_rabbitmq-server resource status will be considered \"bad\"."},{"line_number":22,"context_line":"The status is considered \"good\" when there exists a single master for the"},{"line_number":23,"context_line":"master_p_rabbitmq-server and the rest of the resource instances are reported"}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a016987_c4665a29","line":20,"range":{"start_line":20,"start_character":33,"end_line":20,"end_character":36},"updated":"2015-05-21 16:41:28.000000000","message":"But -\u003e Although","commit_id":"476483fdae835495dbe1bb4f525ca624915069b0"},{"author":{"_account_id":3012,"name":"Dina Belova","email":"dbelova@mirantis.com","username":"dbelova"},"change_message_id":"f5665cff47b0eb3bcf6855f8dcefbcd61424a978","unresolved":false,"context_lines":[{"line_number":52,"context_line":"-------------------------------------------------"},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Normally, failures of the RabbitMQ cluster are automatically healed"},{"line_number":55,"context_line":"by OCF resource agents in Pacemaker. But if this fails for some"},{"line_number":56,"context_line":"reason, there may be unsynchronized queues, wrong cluster membership"},{"line_number":57,"context_line":"reported, or partitions detected by the rabbitmqctl tool, or even"},{"line_number":58,"context_line":"some list channels/queues requests may hang. Note, that the"}],"source_content_type":"text/x-rst","patch_set":4,"id":"7a016987_44294a9d","line":55,"range":{"start_line":55,"start_character":37,"end_line":55,"end_character":40},"updated":"2015-05-21 16:41:28.000000000","message":"But -\u003e although","commit_id":"476483fdae835495dbe1bb4f525ca624915069b0"}]}