[SERVER-50525] Resumable index build hangs waiting for majority commit point in backup_restore_backup_cursor.js Created: 25/Aug/20  Updated: 29/Oct/23  Resolved: 27/Aug/20

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

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

Issue Links:
Related
is related to SERVER-50391 Index build hung during startup recov... Closed
is related to SERVER-36269 Add backup_restore test for backupCur... Closed
is related to SERVER-37192 Move $backupCursor to enterprise Closed
is related to SERVER-49083 Make noPassthrough tests work with re... Closed
is related to SERVER-49847 Turn on resumable index build feature... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-09-07
Participants:

 Description   

In the build variant where resumable index builds are enabled, backup_restore_backup_cursor.js times out while waiting for the majority commit point to advance before continuing the index build.

The majority wait was added in SERVER-48476, which also blacklisted the test by adding the resumable_index_build_incompatible tag. This ticket should investigate the error and decide whether the tag is needed or not.



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

Author:

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

Message: SERVER-50525 re-enable backup_restore_backup_cursor.js for resumable index builds

The underlying issue in the server was fixed in commit 504dee509b57ba039bcfe1130054aabc13839fa9.
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/dd9e2a8a6c345182cef146e1d0edd27a72de8b4a

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