[SERVER-24205] Replicated dbhash command Created: 18/May/16  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Daniel Coupal Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-21939 Ability to force a checkpoint and kee... Closed
is related to SERVER-24173 dbhash should check and/or return ind... Closed
Assigned Teams:
Replication
Participants:

 Description   

Currently, doing a consistency check between replicas involves running dbHash on the instances and comparing them.

It would be nice to have a check that

  • is quicker
  • can be passed to all replicas, through one command
  • does not lock for writes


 Comments   
Comment by Eric Milkie [ 20/May/16 ]

I'm thinking having the dbhash command support a replicated version, where it would put the dbhash into the system log.
You could run this special replicated dbhash command, and it would calculate the hash on each replica via the oplog, so that each replica would presumably be the same data when the dbhash was calculated.
Producing a non-locking dbhash calculation is a different feature request and should get a different ticket. This would be different work in the storage engine.

Generated at Thu Feb 08 04:05:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.