[SERVER-50287] drop_index.js fails when run in passthrough suite with stepdown Created: 13/Aug/20 Updated: 29/Oct/23 Resolved: 03/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.8, 5.0.2, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Yuhong Zhang |
| 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: |
v5.0, v4.4
|
||||||||||||||||
| Sprint: | Execution Team 2021-07-12 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 20 | ||||||||||||||||
| Description |
|
When the jsCore test drop_index.js is run in a replica set passthrough configuration, a stepdown occurring after dropping multiple indexes may result in the subsequent listIndexes command returning one of the dropped indexes. This could be caused by the listIndexes connected to a new primary that may not replicated the oplog entries for both dropped indexes (c_1 and d_1). According to |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 21/Jul/21 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'danielzhangyh@gmail.com', 'username': 'YuhongZhang98'}Message: (cherry picked from commit d8170c86a9b14687ca93df4e18241f05d058f780) |
| Comment by Githook User [ 20/Jul/21 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'danielzhangyh@gmail.com', 'username': 'YuhongZhang98'}Message: (cherry picked from commit d8170c86a9b14687ca93df4e18241f05d058f780) |
| Comment by Githook User [ 02/Jul/21 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'danielzhangyh@gmail.com', 'username': 'YuhongZhang98'}Message: |
| Comment by Benety Goh [ 20/Oct/20 ] |
|
We have a preference for option 3. |
| Comment by Max Hirschhorn [ 13/Aug/20 ] |
|
Here are what I see as the options:
|
| Comment by Benety Goh [ 13/Aug/20 ] |
|
It's possible that we cannot retry this dropIndexes command. The object of this test case is to provide multiple index names in a single invocation. Unrolling the dropIndexes command seems counter to the what |
| Comment by Max Hirschhorn [ 13/Aug/20 ] |
|
benety.goh, I'd expect network_error_and_txn_override.js to be causing the replica_sets_multi_stmt_txn_stepdown_jscore_passthrough.yml test suite to be running the dropIndexes command with w=majority. Is the problem that dropIndexes with multiple indexes cannot be retried because it is possible IndexNotFound would be returned immediately without dropping the other indexes mentioned in the command? I think our stepdown suites are going to want to unroll a dropIndexes with multiple indexes into multiple dropIndexes command with a single index so they can be meaningfully retried then. |