[SERVER-34546] Skip handling EBUSY when in hybrid cursor caching mode Created: 18/Apr/18  Updated: 06/Dec/22  Resolved: 20/Jun/18

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

Type: Task Priority: Major - P3
Reporter: Eric Milkie Assignee: Backlog - Storage Execution Team
Resolution: Incomplete Votes: 0
Labels: nyc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Participants:

 Description   

After SERVER-32424, EBUSY should no longer occur for drop and verify operations, as database locking should prevent any outstanding open cursors on those tables being dropped or verified. We should check to make sure this is the case.
We cannot yet remove the code that handles EBUSY because configuring mongod to use the hybrid cursor caching mode is not compulsory in 4.0.



 Comments   
Comment by Eric Milkie [ 20/Jun/18 ]

It turns out there are still quite a few cases where verify can return EBUSY, even with SERVER-32424. We can revisit this enhancement in the future if the code logic in this area changes.

Generated at Thu Feb 08 04:37:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.