[SERVER-30067] Use ensurePrimaryShard instead of movePrimary in mongos_validate_writes.js Created: 10/Jul/17 Updated: 30/Oct/23 Resolved: 11/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Fixed | 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: | Sharding 2017-07-31 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
movePrimary can return the error 'it is already the primary' and is asserted in mongos_validate_writes.js. Instead, use ensurePrimaryShard, which handles and ignores this error. It's fine to ignore this error because it means that the goal is already accomplished, which randomly may be the case. |
| Comments |
| Comment by Githook User [ 11/Jul/17 ] |
|
Author: {u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}Message: |