[SERVER-7947] Add oplog timestamp to results of stats() and dbHash Created: 15/Dec/12 Updated: 06/Dec/22 Resolved: 09/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Steve Briskin (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | brs | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Add the current oplog timestamp to the results of stats() and dbHash. It would provide a point in time at which those values were valid. I presume both commands take out a lock on the collection. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 09/Aug/18 ] |
|
dbStats and collStats don't operate at an exact cluster-wide point in time. It would be possible to something for dbhash, which supports snapshot isolation within a transaction, but this doesn't seem like a priority at the moment. |
| Comment by Eric Milkie [ 24/Feb/17 ] |
|
Does the metadata now contain this information, and is it included with those commands? |