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
This is the critical issue and must be fixed as soon as possible. When instance is dead for some reason (e.g. tx thread is 100% loaded, while true do end on instance), vshard continues to send requests to it, which fails with TimeOut error. This happens, as connection doesn't die, when tx thread is busy (wait_connected returns true). Manually disabling the instance always fixes the problem, erroneous requests disappear.
ifr:is_connected() and (notprefer_replicaorr~=master) and
replica_check_backoff(r, now) then
returnr
end
r=r.next_by_priority
end
Currently router requests fail way too often, which affects users in mission critical projects. Vshard must try to minimize the number of timed out errors (and probably any other errors). We should consider the following approaches:
But if we choose to fix that ticket, it'll only go to new tarantool releases, leaving vshard installations on old tarantool versions still affected by this bug.
This is the critical issue and must be fixed as soon as possible. When instance is dead for some reason (e.g. tx thread is 100% loaded,
while true do end
on instance), vshard continues to send requests to it, which fails with TimeOut error. This happens, as connection doesn't die, when tx thread is busy (wait_connected
returnstrue
). Manually disabling the instance always fixes the problem, erroneous requests disappear.vshard/vshard/replicaset.lua
Lines 790 to 796 in 2211be2
Currently router requests fail way too often, which affects users in mission critical projects. Vshard must try to minimize the number of
timed out
errors (and probably any other errors). We should consider the following approaches:As a follow up we may introduce the following ticket, but only if smb asks, since it requires user intervention and writing triggers:
The text was updated successfully, but these errors were encountered: