[SERVER-17431] No sharding metadata changes should be allowed if config servers are inconsistent Created: 02/Mar/15  Updated: 27/Oct/15  Resolved: 27/Oct/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.4.6, 2.6.8
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Alexander Komyagin Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:

 Description   

Currently if a config server inconsistency is detected, we only disallow starting new mongoS'es, autosplits and the balancer. However, sharding new collections/databases is allowed, as well as manual chunk splits and moves.

Ongoing manual metadata operations are often triggered by scripts, so if they are not failing it's not possible to detect the erroneous condition.

Further, it's not possible to predict the full scope consequences of metadata alterations when config servers are not consistent.



 Comments   
Comment by Andy Schwerin [ 27/Oct/15 ]

Not an issue since CSRS (SERVER-1448) config servers, which are kept consistent by the replication protocols rather than a special config server write protocol.

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