[SERVER-2544] Two primaries with network partitioned replica set (non-transient) Created: 13/Feb/11 Updated: 12/Jul/16 Resolved: 14/Feb/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.6.5, 1.7.5 |
| Fix Version/s: | 1.7.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sam Bryan | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 9.04 (32bit), Ubuntu 10.04.1 (32bit) |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
Take three hosts in a replica set: config = {_id: 'test1', members: [ sf1 is master. A 'routing issue' occurs ( root@uk1:~# route add -host sf1 reject ), such that: sf1 can talk to ny1. sf1 notices uk1 has gone quiet, and remains a master. (it's a master, it can see a majority, so that's reasonable) Log entries: sf1: ny1: uk1: The impact of this is probably rather mitigated in the real world, as if I repeat this scenario with frequent writes onto sf1, uk1 when partitioned in this way will correctly detect that it's not current ("[rs Manager] replSet info not electing self, we are not freshest"). Relates to forum discussion: http://groups.google.com/group/mongodb-user/browse_thread/thread/b2f01c106f7b6841 |
| Comments |
| Comment by auto [ 13/Feb/11 ] |
|
Author: {u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: eliminate two-primary edge case |