[SERVER-17968] Move configServer.allUp to the catalog manager Created: 09/Apr/15  Updated: 19/Sep/15  Resolved: 15/Apr/15

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

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
Participants:

 Description   

The configServer.allUp method ensures that writes to all three config servers will complete with "high degree of certainty". This method should go inside CatalogManagerLegacy::writeConfigServerDirect.



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

Author:

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

Message: SERVER-17968 Eliminate use of configServer.allUp

Writing directly to config servers is done via ConfigCoordinator::executeBatch
which now checks that all config servers are up.
Branch: master
https://github.com/mongodb/mongo/commit/b5253c0a357dab7ba202fb8368a9f75d72501f17

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