[SERVER-51703] index_secondary_wait_for_commit.js - IndexBuildTest.assertIndexes() sees different server state from IndexBuildTest.getIndexBuildOpId() Created: 16/Oct/20 Updated: 29/Oct/23 Resolved: 21/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| 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 | ||||||||||||||||||||
| Sprint: | Execution Team 2020-11-02 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 21 | ||||||||||||||||||||
| Description |
|
Most tests for index builds, such as index_secondary_wait_for_commit.js use the index_build.js test helper to detect the presence of index builds in the server. We have observed instances where IndexBuildTest.assertIndexes() fails to detect index builds (mostly like because of the operation time used for the read) that were detected by IndexBuildTest.getIndexBuildOpId(), which provides an explicit local read concern to the aggregation command. |
| Comments |
| Comment by Githook User [ 21/Oct/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Benety Goh [ 16/Oct/20 ] |
|
The replication wait suggested in this ticket will also help stabilize the test due to recent changes around secondary reads in |
| Comment by Benety Goh [ 16/Oct/20 ] |
|
This ticket was motivated by a failure in index_secondary_wait_for_commit.js in our CI system. One possible solution that addresses the test failure directly is to await replication before calling IndexBuildTest.assertIndexes(). |