[SERVER-31751] checkReplicatedDataHashes improvements in dumpCollectionDiff Created: 27/Oct/17 Updated: 30/Oct/23 Resolved: 18/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Jonathan Abrahams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | TIG 2017-12-04 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
We only log namespaces next to the hashes, so it can be hard to follow the collection without knowing the UUID. |
| Comments |
| Comment by Jonathan Abrahams [ 18/Nov/17 ] |
|
max.hirschhorn Do we want to backport this for 3.6? |
| Comment by Githook User [ 18/Nov/17 ] |
|
Author: {'name': 'Jonathan Abrahams', 'username': 'hptabster', 'email': 'jonathan@mongodb.com'}Message: |
| Comment by Jonathan Abrahams [ 14/Nov/17 ] |
|
Adding the following to checkReplicatedDataHashes when it dumps collection differences between primary & secondary:
|
| Comment by Benety Goh [ 09/Nov/17 ] |
|
Would be nice to include number of documents in each collection as well. |