[SERVER-49083] Make noPassthrough tests work with resumable index builds Created: 24/Jun/20  Updated: 29/Oct/23  Resolved: 27/Aug/20

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Samyukta Lanka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-50525 Resumable index build hangs waiting f... Closed
is related to SERVER-48476 resumable index build should use majo... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-08-24, Repl 2020-09-07
Participants:

 Description   

SERVER-48476 is adding a wait during index builds that can cause tests to hang for numerous reasons. Tests in noPassthrough that time out because of this are tagged with resumable_index_build_incompatible and blacklisted from running in the resumable index build variant for now. This ticket should address whether these tests are actually incompatible with resumable index builds or not.

The relevant tests are:

  • backup_restore_backup_cursor.js - Failing because something is holding the stable timestamp behind the optime that the node is waiting on. See these logs for more details.
  • indexbg_killop_secondary.js - Failing because heartbeats to the node stuck waiting for the majority commit point to advance are failing (the node is restarting after an expected fassert). See these logs for more details.
  • out_majority_read_replset.js - Failing because replication is stalled on secondaries. This test would normally pass because the commit quorum is disabled.
  • read_majority_reads.js - Failing because it starts a single node replica set and waits for the last optime to be majority committed before it has calculated a stable timestamp. This will prevent the currentCommittedSnapshot from being updated because the stable timestamp isn't moving forward. See these logs.
  • read_majority.js - Same as read_majority_reads.js
  • timestamp_index_builds.js - Failing because the test disables snapshotting on both nodes before the index is created and the operation both nodes need to be majority committed is the startIndexBuild oplog entry, which didn't make it into the snapshot.


 Comments   
Comment by Githook User [ 27/Aug/20 ]

Author:

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

Message: SERVER-49083 Unblacklist indexbg_killop_secondary.js for noPassthrough tests
Branch: master
https://github.com/mongodb/mongo/commit/0a7438226e93c85ce52471478b3440db77b3688b

Comment by Githook User [ 26/Aug/20 ]

Author:

{'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}

Message: SERVER-49083 Unblacklist noPassthrough tests from resumable index builds variant
Branch: master
https://github.com/mongodb/mongo/commit/2deb8086c707bed53fa3b52d6bb20ead6ff1d105

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