[SERVER-51792] index_failover_key_errors.js and indexbg_killop_stepup.js can check indexes before the abort timestamp is reached Created: 21/Oct/20  Updated: 29/Oct/23  Resolved: 16/Nov/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Bug Priority: Major - P3
Reporter: Gregory Noma Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-51703 index_secondary_wait_for_commit.js - ... Closed
related to SERVER-51773 list_indexes_with_build_uuids.js - I... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2020-11-16, Execution Team 2020-11-30
Participants:
Linked BF Score: 21

 Description   

The calls to assertIndexes() in index_failover_key_errors.js and indexbg_killop_stepup.js can end up trying to assert that the index does not exist despite being at an earlier timestamp than the index build's abort timestamp (see these logs). Fixing this may involve a call to awaitReplication() before the assertion.



 Comments   
Comment by Githook User [ 16/Nov/20 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-51792 indexbg_killop_stepup.js and index_failover_key_errors.js wait for replication before calling listIndexes on secondaries
Branch: master
https://github.com/mongodb/mongo/commit/cd30527ec7e4e232574bdaf597c3dc0ac5170b90

Generated at Thu Feb 08 05:26:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.