Closed yarikoptic closed 2 years ago
@yarikoptic The code already retries pushes that fail with "unexpected disconnect" three times; you should see WARNING messages about retries higher up in the log. Is that enough, or should the number of retries be increased?
interesting!
(base) dandi@drogon:/mnt/backup/dandi/dandisets/000108/.git/dandi/logs$ tail -n 10000 sync-20220614151536Z-2927099.log | grep -e 'WARN' -e 'ERROR'
2022-06-16T08:04:14-0400 [WARNING ] backups2datalad git-annex addurl command exited with return code 1
2022-06-16T08:04:14-0400 [ERROR ] backups2datalad Operation failed with exception:
(base) dandi@drogon:/mnt/backup/dandi/dandisets/000108/.git/dandi/logs$ tail -n 100000 sync-20220614151536Z-2927099.log | grep -e 'WARN' -e 'ERROR'
2022-06-16T08:04:14-0400 [WARNING ] backups2datalad git-annex addurl command exited with return code 1
2022-06-16T08:04:14-0400 [ERROR ] backups2datalad Operation failed with exception:
(base) dandi@drogon:/mnt/backup/dandi/dandisets/000108/.git/dandi/logs$ tail -n 100000 sync-20220614151536Z-2927099.log | grep -ie 'warning'
2022-06-16T08:04:14-0400 [WARNING ] backups2datalad git-annex addurl command exited with return code 1
(base) dandi@drogon:/mnt/backup/dandi/dandisets/000108/.git/dandi/logs$ tail -n 100000 sync-20220614151536Z-2927099.log | grep -e 'disconnect; retrying'
grep -e 'disconnect; retrying' sync-20220614151536Z-2927099.log
on the entire log file, might take awhile2
, e.g. 2**i
)
I was staring at 300GB log file (!! woohoo -- even grepping might take hours ;)) for 108 and saw that it ends with an exception
which IMHO shouldn't happen -- we should retry a good reasonable number of times whenever "unexpected" operation happens.