[SERVER-46246] index_failover_resolved_key_errors.js hangs when document level locking is not supported Created: 19/Feb/20  Updated: 29/Oct/23  Resolved: 21/Feb/20

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

Type: Bug Priority: Major - P3
Reporter: Benety Goh 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
is related to SERVER-45351 Newly-elected primaries can commit in... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2020-02-24
Participants:
Linked BF Score: 50

 Description   

This test is designed to perform an update on a collection while an index build is in the collection scan phase. These operations (update, index build scan) require intent exclusive and intent shared locks respectively. Under a storage engine that does not support document level locking, the requested lock modes will be converted to non-intent modes and the collection scan will prevent the update from making progress during the test.



 Comments   
Comment by Githook User [ 20/Feb/20 ]

Author:

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

Message: SERVER-46246 index_failover_resolved_key_errors.js requires support for document level locking
Branch: master
https://github.com/mongodb/mongo/commit/ccb6068e291a50713620eedc3b95caeaf7e2e89f

Comment by Benety Goh [ 19/Feb/20 ]

This test was introduced in SERVER-45351.

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