[SERVER-1330] old mongos processes listed in config.mongos Created: 30/Jun/10 Updated: 21/May/15 Resolved: 30/Jun/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Trivial - P5 |
| Reporter: | Kristina Chodorow (Inactive) | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
I started up three mongos processes and then shut two of them down. However, they were still listed in config.mongos. It seems like we should clean up config.mongos occasionally, as we recommend starting up mongos processes early and often. |
| Comments |
| Comment by Ryan Nitz [ 24/Mar/11 ] |
|
Are you sure you don't want to eventually time these out? This list could grow amazingly large if someone uses something like AWS auto scaling to add/remove nodes (and they run a mongos on each instance). |
| Comment by Eliot Horowitz (Inactive) [ 30/Jun/10 ] |
|
I actually explicitly don't want to do this since I want to have a record of everything. You can look at the ping time though and only look at mongos that are up within 5 minutes or something. |