[SERVER-29827] Improve sharding test to confirm UUID consistency Created: 23/Jun/17 Updated: 25/Sep/17 Resolved: 25/Sep/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ian Whalen (Inactive) | Assignee: | DO NOT USE - Backlog - Test Infrastructure Group (TIG) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | TIG 2017-07-10 | ||||||||
| Participants: | |||||||||
| Description |
|
ReplSetTest.prototype.checkReplicatedDataHashes() verifies that collection options returned by the "listCollections" command are exactly equal on the primary and secondary nodes. This implicitly verifies that the UUID of the collection created on the primary matches the UUID of the collection created on the secondary. We should add a similar kind of validation to ShardingTest to ensure that the UUID for a collection is consistent across all shards. |
| Comments |
| Comment by Max Hirschhorn [ 25/Sep/17 ] |
|
Closing as a duplicate of |