[SERVER-28191] replmonitor_bad_seed.js should await primary node before writing to shard Created: 03/Mar/17 Updated: 06/Dec/17 Resolved: 04/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Spencer Brody (Inactive) |
| 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 | ||||
| Sprint: | Repl 2017-05-08 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
replmonitor_bad_seed.js waits for the replica set nodes to be reachable but if a primary is not available (due to step downs for example), the write to the shard may fail:
We should call ReplSetTest.awaitNodesAgreeOnPrimary on the replica set before executing the sharded write. |
| Comments |
| Comment by Githook User [ 04/May/17 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |