clean shut down of cluster connection when PUT is interrupted
An interrupted `git-annex copy --to` a cluster via the http server, when repeated, failed. The http server output "transfer already in progress, or unable to take transfer lock". Apparently a second connection was opened to the cluster, because the first connection never got shut down. Turned out the problem was that when proxying to a cluster, it would read a short ByteString from the client, and send that to the nodes. But that left the nodes warning more. Meanwhile, the proxy was expecting a SUCCESS/FAILURE message from the nodes. So it didn't return, and so the cluster connection stayed open.
This commit is contained in:
parent
bdde6d829c
commit
5e205f215d
2 changed files with 13 additions and 10 deletions
|
@ -28,12 +28,6 @@ Planned schedule of work:
|
|||
|
||||
## work notes
|
||||
|
||||
* An interrupted `git-annex copy --to` a cluster via the http server,
|
||||
when repeated, fails. The http server outputs "transfer already in
|
||||
progress, or unable to take transfer lock". Apparently a second
|
||||
connection gets opened to the cluster, because the first connection
|
||||
never got shut down.
|
||||
|
||||
* When part of a file has been sent to a cluster via the http server,
|
||||
the transfer interrupted, and another node is added to the cluster,
|
||||
and the transfer of the file performed again, there is a failure
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue