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
If all container nodes refuse to store the object, node throws incomplete object put error. While we are lacking of proper error handling, wrapping latest error message in the chain of put request is better than doing absolutely nothing.
The text was updated successfully, but these errors were encountered:
…eration
In previous implementation Object service's handler returned const error in
case of failure (full or partial) of PUT operation. This did not even allow
us to roughly guess what the reason is. Not as a complete solution, but to
alleviate some cases where all nodes in a container return the same error,
it is suggested to return the error of the last server that responded.
Return latest server error from placement loop of `iteratePlacement` method
of `distributedTarget` type.
Signed-off-by: Leonard Lyubich <leonard@nspcc.ru>
…ompletePut
Make `errIncompletePut` to be a structure which wraps single client error.
Wrap error of the last client into `errIncompletePut` during placement
execution.
Signed-off-by: Leonard Lyubich <leonard@nspcc.ru>
If all container nodes refuse to store the object, node throws
incomplete object put
error. While we are lacking of proper error handling, wrapping latest error message in the chain of put request is better than doing absolutely nothing.The text was updated successfully, but these errors were encountered: