[SERVER-18267] Don't leak mongos consistency checker thread Created: 30/Apr/15 Updated: 19/Sep/15 Resolved: 07/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.1.2 |
| Fix Version/s: | 3.1.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Alabi | Assignee: | Daniel Alabi |
| Resolution: | Done | Votes: | 0 |
| Labels: | UT | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Participants: |
| Description |
|
The consistency checker thread periodically checks that the config servers have the same content. Residing in the legacy catalog manager, that thread is intentionally not being joined. Joining the thread on shutdown of the catalog manager makes each sharding test run much slower probably because the thread, on every iteration, sleeps for 60s and also runs a rather costly dbhash on the config collections. |
| Comments |
| Comment by Githook User [ 07/May/15 ] |
|
Author: {u'username': u'alabid', u'name': u'Daniel Alabi', u'email': u'alabidan@gmail.com'}Message: |