Details
-
Bug
-
Resolution: Works as Designed
-
Major - P3
-
None
-
None
-
None
-
None
-
Storage Execution
-
ALL
-
Execution Team 2022-02-21, Execution Team 2022-03-21
Description
On Windows, killing a backup cursor while still copying from it will cause an invariant (since WT cannot delete the file).
This was found during file copy based initial sync testing; I will also file a ticket to not do this, but crashing seems undesirable anyway.
[j0:prim] | 2021-11-09T14:08:02.331+00:00 D2 COMMAND 21965 [conn131] "About to run the command","attr":{"db":"admin","client":"127.0.0.1:54849","commandArgs":{"killCursors":"$cmd.aggregate","cursors":[3906021346930736600],"$db":"admin"}}
|
[j0:prim] | 2021-11-09T14:08:02.331+00:00 E STORAGE 22435 [conn131] "WiredTiger error","attr":{"error":16,"message":"[1636466882:330745][5124:140706774209120], WT_CURSOR.close: int __cdecl __win_fs_remove(struct __wt_file_system *,struct __wt_session *,const char *,unsigned int), 81: \\data\\db\\job0\\resmoke\\node0\\WiredTiger.backup: file-remove: DeleteFileW: The process cannot access the file because it is being used by another process.\r\n: Resource device"}
|
[j0:prim] | 2021-11-09T14:08:02.331+00:00 F ASSERT 23083 [conn131] "Invariant failure","attr":{"expr":"_session->close(_session, nullptr)","error":"ObjectIsBusy: 16: Resource device","file":"src\\mongo\\db\\storage\\wiredtiger\\wiredtiger_session_cache.cpp","line":78}
|
[j0:prim] | 2021-11-09T14:08:02.331+00:00 F ASSERT 23084 [conn131] "\n\n***aborting after invariant() failure\n\n"
|
[j0:prim] | 2021-11-09T14:08:02.331+00:00 F CONTROL 4757800 [conn131] "Writing fatal message","attr":{"message":"Got signal: 22 (SIGABRT).\n"}
|
[j0:prim] | 2021-11-09T14:08:02.332+00:00 I COMMAND 51803 [conn132] "Slow query","attr":{"type":"command","ns":"admin.$cmd.aggregate","appName":"FileCopyBasedInitialSyncer","command":{"aggregate":1,"pipeline":[{"$_backupFile":{"backupId":{"$uuid":"0e76c891-3922-4a93-9fbf-5ace9f44756e"},"file":"\\data\\db\\job0\\resmoke\\node0\\WiredTiger.backup","byteOffset":0}}],"cursor":{"batchSize":101},"readConcern":{},"writeConcern":{"w":1,"wtimeout":0},"$readPreference":{"mode":"secondaryPreferred"},"$db":"admin"},"keysExamined":0,"docsExamined":0,"cursorExhausted":true,"numYields":0,"nreturned":1,"reslen":170033,"locks":{},"readConcern":{"provenance":"implicitDefault"},"writeConcern":{"w":1,"wtimeout":0,"provenance":"clientSupplied"},"remote":"127.0.0.1:54852","protocol":"op_msg","durationMillis":14}
|
Attachments
Issue Links
- related to
-
SERVER-61344 Make sure cloning is complete before killing the backup cursor
-
- Closed
-