context.Cancelled
and context.DeadlineExceeded
reasons for client sleep
#24
Labels
enhancement
New feature or request
help wanted
Extra attention is needed
question
Further information is requested
triage
Context
After the nspcc-dev#2164, any
error
returned by a client (means realerror
, non-status (SplitInfo
is an exception)) makes all the following requests to the client fail. That could help with some high-load (or failover) scenarios.Problem
On the other hand, I do not totally agree that such a solution should be considered our best effort. At least
context.Cancelled
is not clear at all to me.Thoughts
I guess we can tune network communication, turn the
Replicator
off for some time, add some feedback mechanism for our components, etc, but not only sleep for30s
and hope that everything will be fine. Moreover, the current implementation will still read objects from disk and fail and the almost latest step (HEAD
, before the finalPUT
). Also, does anybody ever think about the "pull" replication mechanism vs the current "push"?The text was updated successfully, but these errors were encountered: