Bug 1138213

Summary: Rabbitmq cluster remains partitioned after short network partition incident
Product: [Fedora] Fedora Reporter: Jan Provaznik <jprovazn>
Component: rabbitmq-serverAssignee: Peter Lemenkov <lemenkov>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: erlang, hubert.plociniczak, jeckersb, lemenkov, rjones, s
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 22:23:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jan Provaznik 2014-09-04 09:46:10 UTC 
Description of problem:
In 3-node rabbitmq cluster after network partition happens and then when 3 nodes can communicate again, then cluster remains partitioned if "pause_minority" policy is used.

This happens if network outage is short enough (~60secs), for longer outages (>3 minutes) cluster was reconstructed properly. Very similar issue was reported here:
http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2014-March/034639.html

This issue seems to be fixed in upstream already (not sure in which version exactly, but 3.3.5 works fine).

Version-Release number of selected component (if applicable):
rabbitmq-server-3.1.5-9.fc20.noarch

Steps to Reproduce:
1. create 3-node cluster, use "pause_minority" no-quorum policy
2. stop networking on one of nodes and wait until the node is seen as shutdown on other nodes
3. start networking on the node again

Actual results:
Cluster remains partitioned:

[root@overcloud-controller1-csugetg5pjql ~]# rabbitmqctl cluster_status
Cluster status of node 'rabbit@overcloud-controller1-csugetg5pjql' ...
[{nodes,
     [{disc,
          ['rabbit@overcloud-controller0-o6yt2gtaxk6g',
           'rabbit@overcloud-controller1-csugetg5pjql',
           'rabbit@overcloud-controller2-z3tswnamdzhq']}]},
 {running_nodes,
     ['rabbit@overcloud-controller0-o6yt2gtaxk6g',
      'rabbit@overcloud-controller1-csugetg5pjql']},
 {partitions,
     [{'rabbit@overcloud-controller0-o6yt2gtaxk6g',
          ['rabbit@overcloud-controller2-z3tswnamdzhq']},
      {'rabbit@overcloud-controller1-csugetg5pjql',
          ['rabbit@overcloud-controller2-z3tswnamdzhq']}]}]
...done.


Expected results:
no partitiones after the node is up again


Additional info:
only related message in log:
Mnesia('rabbit@overcloud-controller0-o6yt2gtaxk6g'): ** ERROR ** mnesia_event got {inconsistent_database, running_partitioned_network, 'rabbit@overcloud-controller2-z3tswnamdzhq'}
Comment 1 John Eckersberg 2014-09-04 12:53:15 UTC 
I built 3.3.5 for rawhide recently.  Here's a scratch build for f20 if you want to give it a try:

http://koji.fedoraproject.org/koji/taskinfo?taskID=7522486

You might have to set selinux permissive to get it to start on f20 (see bug 1135523 for more info).
Comment 2 Fedora End Of Life 2015-05-29 12:47:42 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 3 Fedora End Of Life 2015-06-29 22:23:14 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.