Bug #3352: [SDK] After ^C, arv-put sometimes exits but leaves processes/threads behind that keep the resume file locked, preventing retrying the aborted arv-put. - Arvados

Actions

Copy link

Bug #3352

closed

[SDK] After ^C, arv-put sometimes exits but leaves processes/threads behind that keep the resume file locked, preventing retrying the aborted arv-put.

Added by Tom Clegg over 9 years ago. Updated about 7 years ago.

Status:

Closed

Priority:

Normal

Assigned To:

Category:

Target version:

Story points:

1.0

Actions

Copy link

Updated by Tom Clegg over 9 years ago

Target version set to Arvados Future Sprints

Actions

Copy link

Updated by Brett Smith over 9 years ago

I think the most likely explanation is that these are KeepWriterThreads (see keep.py) that are still in the middle of I/O and so don't get the SIGINT. At the very least, arv-put should put up some kind of "cleaning up" message and wait until they're done. If it can encourage the threads to end so the user can restart sooner, that's even better. If not, another alternative is to at least let go of the cache lock--after we do our last write, it's okay for another arv-put to take it over.

Actions

Copy link