[SDK] After ^C, arv-put sometimes exits but leaves processes/threads behind that keep the resume file locked, preventing retrying the aborted arv-put.
|Velocity based estimate||0 days|
#2 Updated by Brett Smith about 3 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.