[SERVER-33471] Archival should retry if a file cannot be added to the tar Created: 23/Feb/18  Updated: 14/Aug/23  Resolved: 14/Aug/23

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.1 Desired

Type: Task Priority: Major - P3
Reporter: Jonathan Abrahams Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Won't Fix Votes: 1
Labels: stm, tig-qwin-eligible
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-33470 Log archival message, even if success... Closed
Assigned Teams:
Server Tooling & Methods
Participants:
Linked BF Score: 0

 Description   

There are situations that the tarfile.add will fail for an open file and it is ignored. A retry mechanism should be investigated.



 Comments   
Comment by Alex Neben [ 14/Aug/23 ]

We have not seen this issue recently. We are also working on the hang analyzer right now and this ticket looks stale.

Comment by Eric Milkie [ 03/Oct/18 ]

I'm linking another related BFG that didn't capture all the data files due to a problem adding a particular file to the tar. 

Comment by Max Hirschhorn [ 27/Feb/18 ]

We should investigate whether retries would help capturing files that are currently open by the server on Windows. We should otherwise consider capturing a second data archive after the server has been terminated.

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