[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:
Related
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:
https://github.com/mongodb/docs/pull/1736



 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: DOCS-3214: backport of changes to movePrimary
Branch: v2.4
https://github.com/mongodb/docs/commit/a11214d3794b44e400c22524d2d4ac467e80f263

Comment by Githook User [ 01/May/14 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-3214: clarification and style
Branch: master
https://github.com/mongodb/docs/commit/d832f9131cdd3718ead19ec4723e3ce11b7ebb4f

Generated at Thu Feb 08 07:45:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.