[SERVER-21223] MongoS can't be shut down for at least 1.5 minutes if a legacy config server is unreachable Created: 30/Oct/15 Updated: 06/Dec/22 Resolved: 21/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Kaloian Manassiev | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Operating System: | ALL |
| Participants: |
| Description |
|
The legacy catalog manager initialization code sleeps for 10 seconds and then retries, if a config server host cannot be reached. This may delay shutdown of MongoS or MongoD by at least 1.5 minutes, because it ignores the isShutdown bit. This always happens with MongoS, but on MongoD only happens in the presence of minOpTime recovery information, because We should make it check for the isShutdown bit. |
| Comments |
| Comment by Andy Schwerin [ 21/Oct/16 ] |
|
No field reports. Workaround is to just send a kill signal tot he mongos, which is safe. |