[SERVER-11398] Metadata should become read-only when mongos detects config databases being different Created: 26/Oct/13 Updated: 06/Dec/22 Resolved: 15/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.4.14 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alexander Komyagin | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
2 shards, 3 config servers |
||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
If mongos detects that config servers are different, metadata should not be changed.
I checked manually with 2.4.1, and I could do manual splitAt and moveChunk, while my second config server was out of sync. |
| Comments |
| Comment by Kaloian Manassiev [ 15/Dec/17 ] |
|
This problem is only present in config servers using the SCCC configuration. Starting with 3.2 it is no longer a problem with CSRS. |
| Comment by vishalbenbanshi [ 28/Oct/13 ] |
|
igo to market |