[SERVER-13627] Disallow 0-vote arbiters Created: 17/Apr/14 Updated: 27/Oct/15 Resolved: 03/Jun/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.6.0 |
| Fix Version/s: | 2.7.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Matt Dannenberg |
| Resolution: | Done | Votes: | 0 |
| Labels: | cap-ticket-needed, pull-request | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
I was able to reconfigure giving arbiter node "votes:0" which was accepted. This seems very wrong and we should reject that as invalid combination of options.
|
| Comments |
| Comment by Githook User [ 12/Nov/14 ] |
|
Author: {u'username': u'ajdavis', u'name': u'A. Jesse Jiryu Davis', u'email': u'jesse@mongodb.com'}Message: This re-applies commit 6eccc037b1e6d22d60d0e7aec39dcc183a756790 with a fix Don't assume that the first member started is always the primary. Closes #856 Signed-off-by: Benety Goh <benety@mongodb.com> |
| Comment by Githook User [ 04/Nov/14 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: Revert " This reverts commit 6eccc037b1e6d22d60d0e7aec39dcc183a756790. |
| Comment by Githook User [ 04/Nov/14 ] |
|
Author: {u'username': u'ajdavis', u'name': u'A. Jesse Jiryu Davis', u'email': u'jesse@mongodb.com'}Message: Closes #856 Signed-off-by: Benety Goh <benety@mongodb.com> |
| Comment by Eric Milkie [ 15/Oct/14 ] |
|
After some discussion, we decided that the state should be UNKNOWN and this is expected behavior, when dealing with mixed replica sets and invalid configs. |
| Comment by A. Jesse Jiryu Davis [ 15/Oct/14 ] |
|
Adding a 2.8 arbiter with 0 votes to a 2.6 replica set appears to work (replSetReconfig returns "ok"). But the arbiter itself logs "REPLSETS [rsStart] replSet cfg parsing exception for members[3] arbiter must vote (cannot have 0 votes)" and refuses to join. It remains in state UNKNOWN. Is this as designed, or should it move to state REMOVED? |
| Comment by Eric Milkie [ 15/Oct/14 ] |
|
jesse to confirm, were you testing a build with "--replication-implementation=impl"? |
| Comment by A. Jesse Jiryu Davis [ 15/Oct/14 ] |
|
There are two error codes associated with this prohibition: trying to add a 0-vote arbiter with replSetReconfig causes an error 13135, but trying to replSetInitiate with an initial config that includes a 0-vote arbiter causes error 93. Is this expected or a bug? |
| Comment by Githook User [ 03/Jun/14 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |
| Comment by Matt Dannenberg [ 30/May/14 ] |
|
reopening due to revert due to majority.js depending on the bad behavior |
| Comment by Githook User [ 30/May/14 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: Revert " This reverts commit 07838d04bece908d12d7f0ded46a0a75ff77608f. |
| Comment by Githook User [ 30/May/14 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |