[SERVER-35097] Run CheckReplOplogs in sharded passthroughs Created: 18/May/18 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication, Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | tig-dataconsistency | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Tooling & Methods
|
| Participants: | |
| Story Points: | 3 |
| Description |
|
Currently it isn't supported for sharded clusters, but dbhash failures without oplog checks often miss the underlying cause. |
| Comments |
| Comment by Steven Vannelli [ 10/May/22 ] |
|
Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions. |
| Comment by Max Hirschhorn [ 21/Jun/18 ] |
|
We should model this off of how the run_check_repl_dbhash.js hook discovers the CSRS and replica set shards in order to run the ReplSetTest#checkReplicatedDataHashes() function on them. We can abstract out running some function defined on ReplSetTest in a thread per replica set. |