You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having two nodes, A and B, disconnecting a single node during running GetRange request, makes GetRange request never end. Same happens if the request uses a single node and it disconnects - the request never ends.
Since the DLS node never resumes the request, disconnecting the client should simply count towards finished nodes. In general, I think we should take this in the careful consideration when implementing the Continue after disconnect - this should not be allowed if the client requested stop.
The text was updated successfully, but these errors were encountered:
Unrelated to the re-connection problem, there's a problem when the node was not available when the request started - the request will wait in the request's connector to connect to the node.
Having two nodes,
A
andB
, disconnecting a single node during runningGetRange
request, makesGetRange
request never end. Same happens if the request uses a single node and it disconnects - the request never ends.Since the DLS node never resumes the request, disconnecting the client should simply count towards finished nodes. In general, I think we should take this in the careful consideration when implementing the
Continue
after disconnect - this should not be allowed if the client requestedstop
.The text was updated successfully, but these errors were encountered: