[SERVER-24466] replsettest getPrimary() should only return when there is exactly one node in the primary state Created: 08/Jun/16 Updated: 07/Dec/16 Resolved: 09/Jun/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Completed: | |||||
| Sprint: | Repl 16 (06/24/16) | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Currently if two nodes think that they are Primary, whichever getPrimary() calls isMaster on last will be returned. calls to getPrimary() are often followed by writes to the primary which will fail if that primary steps down soon after being returned. |
| Comments |
| Comment by Githook User [ 09/Jun/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: (cherry picked from commit 2559d31fe46d0cbabe19b7084cadd438f3e13d33) |
| Comment by Githook User [ 09/Jun/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |