[SERVER-21019] MongoS service does not restart as per service defined behaviour if all config servers are down Created: 19/Oct/15 Updated: 24/Jun/19 Resolved: 24/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 3.0.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Anil Kumar | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
v3.0.4, Windows 7 |
||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
On a single-replicaset environment with a MongoS, all servers (mongoD, mongoS and 3 config servers) are configured as Windows services. All services have recovery actions that should cause Windows to restart the services 10 seconds later. Following command is used to specify the recovery action:
If all 3 config servers are stopped and the a MongoS is started, MongoS exits (expected), however it does not automatically restart after 10 seconds as specified in the above mentioned service configuration command. Following is the output of the sc query mongos:
The suspicion is that the Windows doesn't restart MongoS that was exited with a state STOPPED instead of PAUSED. |
| Comments |
| Comment by Ramon Fernandez Marina [ 14/Oct/16 ] | ||||||||||||||
|
Hi alessandro.gherardi@yahoo.com, I'm glad to hear you're not seeing this issue in 3.2.9, although I'm not aware of any modification on our end that could have accounted for the behavior change – I'll take a closer look. Thanks, | ||||||||||||||
| Comment by Alessandro Gherardi [ 14/Oct/16 ] | ||||||||||||||
|
Any updates? | ||||||||||||||
| Comment by Alessandro Gherardi [ 23/Sep/16 ] | ||||||||||||||
|
I switched to using config server replica sets with Mongo 3.2.9 in my development environment and this issue no longer occurs. Can you please confirm this is by design and if so close this ticket? Thank you in advance. | ||||||||||||||
| Comment by Alessandro Gherardi [ 10/Mar/16 ] | ||||||||||||||
|
If I call:
and the config servers are down, the mongoS service cannot be stopped via "net stop MongoS". The only way to recover is to set the failureflag back to 0, then call "net stop MongoS". In other words, I don't think that setting failureflag to 1 is a viable solution. | ||||||||||||||
| Comment by Mark Benvenuto [ 20/Oct/15 ] | ||||||||||||||
|
It depends on the following setting being 1.
See https://msdn.microsoft.com/en-us/library/windows/desktop/ms685937(v=vs.85).aspx for more information. |