[SERVER-49774] Enable rollback testing for resumable index builds in the collection scan phase Created: 21/Jul/20  Updated: 29/Oct/23  Resolved: 02/Sep/20

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

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

Issue Links:
Depends
depends on SERVER-50168 Transition to rollback doesn't need t... Closed
Related
related to SERVER-49075 Add replica_sets suite to resumable i... Closed
related to SERVER-49076 Add rollback fuzzer suites to resumab... Closed
is related to SERVER-48418 Rollback restart resumable index buil... Closed
is related to SERVER-48476 resumable index build should use majo... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-08-10, Execution Team 2020-08-24, Execution Team 2020-09-07
Participants:

 Description   

After SERVER-50168, this work should simply entail enabling rollback_resumable_index_build_collection_scan_phase.js.

Original description:

If a node goes into rollback during the collection scan of a resumable index build, the majority committed view gets zeroed out which causes the scan to throw ReadConcernMajorityNotAvailableYet. We then hit this invariant since we currently do not expect an index build to fail this way.



 Comments   
Comment by Githook User [ 02/Sep/20 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-49774 Enable rollback testing for resumable index builds in the collection scan phase
Branch: master
https://github.com/mongodb/mongo/commit/30e0f2a2b33a9b87259ac4c8a9e19518e2b8e1a3

Comment by Suganthi Mani [ 10/Aug/20 ]

Response to my previous question - the index build collection started during STARTUP state doesn't use majority committed snapshot cursor. So, we can't get "ReadConcernMajorityNotAvailableYet" error.

Comment by Suganthi Mani [ 10/Aug/20 ]

gregory.noma benety.goh, tess.avitabile raised a valid question while triaging for SERVER-50168's whether it's possible for index build's collection scan to get the same error "ReadConcernMajorityNotAvailableYet" in replication STARTUP state . If so, SERVER-50168 fix won't be sufficient. Let me know your thoughts on it.

Comment by Benety Goh [ 06/Aug/20 ]

This ticket is on hold until SERVER-50168 is triaged.

Comment by Benety Goh [ 21/Jul/20 ]

One of the test cases added in SERVER-48418 provides test coverage for the issue in this ticket. That test case will remain disabled with a TODO comment referencing this ticket.

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