mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2021-12-01 12:46:07 -04:00
parent 7ca799efed
commit e11ca04e28
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 18 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

18
doc/bugs/annex_get_should_retry_failed_downloads_from_S3/comment_1_4de90238d57de0d49b75418411135dbc._comment Normal file
View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2021-12-01T16:39:05Z"
content="""
It seems that every failure in that log is preceeded by "transfer already
in progress, or unable to take transfer lock".
It does not make sense to retry in such a case because the transfer will
probably still be in progress so the retry would fail.
So I don't think this really involves retrying (which certianly supports
S3). The question is why are several transfers failing this way.
My suspicion would be something to do with pid locking.
And indeed, I can reproduce the same behavior in a local repo getting from
another local repo, once I set annex.pidlock.
"""]]