[SERVER-36869] fsm capped collection checks should only make 1 query for assertions Created: 24/Aug/18 Updated: 29/Oct/23 Resolved: 27/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.3, 4.1.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Bradford (Inactive) | Assignee: | David Bradford (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 11 | ||||||||||||
| Description |
|
In the fsm workloads create_capped_collection.js and create_capped_collection_maxdocs.js, we check the number of documents after truncations and the actual documents. This is done with 2 queries and the number of documents is used to assert that the actual documents are correct. The problem is if the stepdown thread is running and the primary steps down between the 2 queries the results may not be consistent since capped collections are maintained independently in the replica set. The same assertion could be done with a single query, which would remove the window in which a stepdown could cause problems. |
| Comments |
| Comment by Githook User [ 03/Sep/18 ] |
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: |
| Comment by Githook User [ 31/Aug/18 ] |
|
Author: {'name': 'David Bradford', 'email': 'david.bradford@mongodb.com', 'username': 'dbradf'}Message: (cherry picked from commit 8143b34ed3ff6cb5eeecbc8f8cd9f009a82fe9c1) |
| Comment by Githook User [ 27/Aug/18 ] |
|
Author: {'name': 'David Bradford', 'email': 'david.bradford@mongodb.com', 'username': 'dbradf'}Message: |