[SERVER-23306] Check collection attributes during (js) testing Created: 23/Mar/16 Updated: 18/Nov/16 Resolved: 05/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.9, 3.3.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Jonathan Abrahams |
| Resolution: | Done | Votes: | 0 |
| Labels: | test-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Completed: | |||||||||||||||||
| Sprint: | TIG 15 (06/03/16), TIG 17 (07/15/16) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
When running test suites which verify replication we should not only compare the collection list, but also attributes like "capped" and "temp", which are part of the output of the commands collStats and listCollections More Attributes:
|
| Comments |
| Comment by Githook User [ 18/Jul/16 ] | ||||||||||||||||||
|
Author: {u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}Message: (cherry picked from commit 71424c1c4b87c5819b1fc5cf114078a6f33c6078) | ||||||||||||||||||
| Comment by Githook User [ 05/Jul/16 ] | ||||||||||||||||||
|
Author: {u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}Message: | ||||||||||||||||||
| Comment by Robert Guo (Inactive) [ 22/Jun/16 ] | ||||||||||||||||||
|
I re-purposed this ticket to check for more attributes. The original description of checking for the "capped" and "temp' attributes are done as part of | ||||||||||||||||||
| Comment by Max Hirschhorn [ 23/Mar/16 ] | ||||||||||||||||||
|
The CheckReplDBHash hook in resmoke.py already verifies that if the collection is capped on the primary, then it should be capped on the secondary (and vice-versa).
The primary_coll_hash == secondary_coll_hash check should probably be moved after calling the "collStats" command to avoid the situation where a collection is capped on the primary and non-capped on the secondary, but has a maxSize such that the collection has yet to be truncated. We may want to consider addressing this issue when porting the hook to JS in |