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
rabbit_feature_flags: Retry after erpc:call() fails with noconnection
[Why]
There could be a transient network issue. Let's give a few more chances
to perform the requested RPC call.
[How]
We retry until the given timeout is reached, if any.
To honor that timeout, we measure the time taken by the RPC call itself.
We also sleep between retries. Before each retry, the timeout is reduced
by the total of the time taken by the RPC call and the sleep.
References #8346.
V2: Treat `infinity` timeout differently. In this case, we never retry
following a `noconnection` error. The reason is that this timeout is
used specifically for callbacks executed remotely. We don't know how
long they take (for instance if there is a lot of data to migrate).
We don't want an infinite retry loop either, so in this case, we
don't retry.
0 commit comments