[SERVER-20085] Additional consistency validation checks for config servers as replica sets Created: 21/Aug/15 Updated: 06/Dec/22 Resolved: 30/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Alexander Komyagin | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
I believe we are deprecating the dbHash functionality as of 3.2, given that we are switching to the replica set architecture for the config database. Although replica sets are designed to have [eventual] consistency among their nodes, inconsistencies in the config db can render a sharded cluster unusable. Thus it seems reasonable to implement additional validation mechanism(s) in the unlikely event of consistency issues. For example, we could periodically check the consistency of config repl set members. |