[SERVER-46957] Implement quiesce mode on mongos Created: 18/Mar/20 Updated: 29/Oct/23 Resolved: 13/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Pavithra Vetriselvan |
| 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-05-04, Repl 2020-05-18 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||
| Description |
|
In the mongos shutdown procedure here, ask the MongosTopologyCoordinator to increment the topologyVersion and start responding to isMaster requests with ok:0. Initially the quiesce time should be 100ms. Test that the server status metrics for waiting isMaster requests are updated correctly. |
| Comments |
| Comment by Pavithra Vetriselvan [ 14/May/20 ] |
|
Not sure why the Githook User didn't work here, but this is the corresponding commit on master: |