[SERVER-38402] closeAll_with_background_ops_fails_safely relies on an incorrect assumption Created: 04/Dec/18  Updated: 06/Dec/22  Resolved: 16/Mar/20

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

Type: Bug Priority: Minor - P4
Reporter: Daniel Gottlieb (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Assigned Teams:
Storage Execution
Operating System: ALL
Backport Requested:
v4.0
Participants:
Linked BF Score: 21

 Description   

The test attempts to assert that restarting the catalog will correctly restore any state in the event the operation fails. To do this it starts a background index build (which causes closing the catalog to fail), then calls restartCatalog. However, the test calls restartCatalog after it observes the index build in currentOp, which it turns out is not sufficient. The server code will first register the command in CurOp before marking it as a BackgroundOperation. Thus it's possible for the restartCatalog to succeed as it can come in before the index build marks itself as a BackgroundOperation.


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