[SERVER-48468] Update sharding architecture guide for quiesce mode Created: 28/May/20 Updated: 29/Oct/23 Resolved: 02/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Tess Avitabile (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 | ||||||||
| Sprint: | Repl 2020-07-13 | ||||||||
| Participants: | |||||||||
| Comments |
| Comment by Githook User [ 01/Jul/20 ] |
|
Author: {'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}Message: |
| Comment by Githook User [ 29/May/20 ] |
|
Author: {'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}Message: |
| Comment by Tess Avitabile (Inactive) [ 29/May/20 ] |
|
Sounds good, thank you! |
| Comment by Esha Maharishi (Inactive) [ 28/May/20 ] |
|
Hmm. Happy to have replication update the sharding arch guide for quiesce mode, though I'm thinking about what section it should go in. alex.taskov is going to add a section on sharding component initialization and shutdown ( How about we renameĀ this section to "Node startup and shutdown" and make it have two subsections, one that Alex is adding and one called "Quiesce mode on shutdown" (or similar) that replication can fill in? |
| Comment by Tess Avitabile (Inactive) [ 28/May/20 ] |
|
esha.maharishi, we're updating the Replication architecture guide to contain a sentence on quiesce mode. Shall we update the Sharding architecture guide too, or would you prefer Sharding do so? If Replication does it, what section should it go in? I could imagine either having a section on TopologyVersion or on shutdown. For a section on TopologyVersion, I would make the text something like, "mongos has a TopologyVersion, which it updates on significant topology changes (anything that affects the response to isMaster). The isMaster command awaits changes in the TopologyVersion before returning. Currently, the only significant topology change is entering quiesce mode: the mongos increments the TopologyVersion and starts responding to isMaster commands with a ShutdownInProgress error, so that clients cease routing new operations to the node." |