[SERVER-18125] Move config server consistency checking behind the legacy catalog manager Created: 20/Apr/15  Updated: 19/Sep/15  Resolved: 30/Apr/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.1.3

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Daniel Alabi
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2 04/24/15, Sharding 3 05/15/15
Participants:

 Description   

The config server checker thread (config_server_checker_service.cpp) needs to move behind the catalog manager. The associated dbtests need to either be removed or changed to standalone unit-tests.



 Comments   
Comment by Githook User [ 30/Apr/15 ]

Author:

{u'username': u'alabid', u'name': u'Daniel Alabi', u'email': u'alabidan@gmail.com'}

Message: SERVER-18125 Don't join consistency checker thread

Before 336085ecb5e457194843d920eae5b0d42ea8b4b0, we leaked the thread.
But now, each sharding test runs much slower when we join the consistency checker
sharding thread probably because the thread sleeps for 60s on every iteration
and also runs dbhash on the config collections.
Branch: master
https://github.com/mongodb/mongo/commit/82596f0aa2dda84b1bc97c8e0be2def934fe81da

Comment by Githook User [ 29/Apr/15 ]

Author:

{u'username': u'alabid', u'name': u'Daniel Alabi', u'email': u'alabidan@gmail.com'}

Message: SERVER-18125 Move config server consistency checking behind the legacy catalog manager
Branch: master
https://github.com/mongodb/mongo/commit/336085ecb5e457194843d920eae5b0d42ea8b4b0

Generated at Thu Feb 08 03:46:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.