[DOCS-3214] Tighten conditions when it's safe to use movePrimary Created: 18/Apr/14 Updated: 01/May/14 Resolved: 01/May/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Thomas Rueckstiess | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 41 weeks, 6 days ago | ||||
| Description |
|
The conditions when it is safe to call movePrimary need to be tighter than currently documented, and we should mention that the other mongos do not know about the change until restarted/flushRouterConfig'ed. I wrote a draft, here the pull request: |
| Comments |
| Comment by Githook User [ 01/May/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 01/May/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |