[SERVER-41968] IndexBuildTest.getIndexBuildOpId() not selective enough when IndexBuildsCoordinator is enabled Created: 27/Jun/19 Updated: 29/Oct/23 Resolved: 07/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1, 4.2.4 |
| 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 | ||||||||||||||||||||||||||||
| Backport Requested: |
v4.2
|
||||||||||||||||||||||||||||
| Sprint: | Execution Team 2019-07-01, Execution Team 2019-07-15 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Linked BF Score: | 20 | ||||||||||||||||||||||||||||
| Description |
|
When the primary is building the index with the IndexBuildsCoordinator, there could be two db.currentOp() entries for the index build: one for the command invocation on the client connection and another for the task in the thread pool managed by the IndexBuildsCoordinator. The operation performing the actual work should be the one with a non-empty 'locks' field and should be preferred over the client connection operation. This affects mostly JS tests that attempt to locate and modify the state of an active index build when the enableIndexBuildsCoordinatorForCreateIndexesCommand server parameter is enabled. |
| Comments |
| Comment by Githook User [ 19/Feb/20 ] |
|
Author: {'username': 'benety', 'name': 'Benety Goh', 'email': 'benety@mongodb.com'}Message: (cherry picked from commit 0fd75d9f6abdd3423882ec03b3b3f851f7207c4a) |
| Comment by Githook User [ 19/Feb/20 ] |
|
Author: {'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}Message: This ensures that we are getting sufficient coverage over the side table logic. (cherry picked from commit 1aeaff5c35321a3ffb7e0dbc08c59f633e1dedbf) |
| Comment by Githook User [ 19/Feb/20 ] |
|
Author: {'username': 'benety', 'name': 'Benety Goh', 'email': 'benety@mongodb.com'}Message: (cherry picked from commit fc04ae1ec734645c1f8e2828c0a367192d5bc0ec) |
| Comment by Githook User [ 19/Feb/20 ] |
|
Author: {'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}Message: This affects mostly index builds that use the IndexBuildsCoordinator because there (cherry picked from commit 82177ac1ee32044a733be742b8244eff9389a9fc) |
| Comment by Githook User [ 19/Feb/20 ] |
|
Author: {'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}Message: (cherry picked from commit 75bf2309c8eda5496c5b4a022bd5168950eda7eb) |
| Comment by Githook User [ 19/Feb/20 ] |
|
Author: {'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}Message: (cherry picked from commit 335a4e981228156ebc92e87065b817244e5084d6) |
| Comment by Githook User [ 07/Jul/19 ] |
|
Author: {'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}Message: |
| Comment by Githook User [ 07/Jul/19 ] |
|
Author: {'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}Message: This ensures that we are getting sufficient coverage over the side table logic. |
| Comment by Githook User [ 06/Jul/19 ] |
|
Author: {'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}Message: |
| Comment by Githook User [ 06/Jul/19 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: This affects mostly index builds that use the IndexBuildsCoordinator because there |
| Comment by Githook User [ 05/Jul/19 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Githook User [ 05/Jul/19 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |