Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rabbit_feature_flags: Retry after erpc:call() fails with noconnection (backport #8411) #8491

Merged
merged 2 commits into from
Jun 6, 2023

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Jun 6, 2023

This is an automatic backport of pull request #8411 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[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.
(cherry picked from commit 8749c60)
[Why]
This is unused in this source file.

(cherry picked from commit f09544b)
@dumbbell dumbbell merged commit 0c9d55b into v3.12.x Jun 6, 2023
16 checks passed
@dumbbell dumbbell deleted the mergify/bp/v3.12.x/pr-8411 branch June 6, 2023 14:24
dumbbell added a commit that referenced this pull request Jun 6, 2023
rabbit_feature_flags: Retry after `erpc:call()` fails with `noconnection` (backport #8411) (backport #8491)
@dumbbell dumbbell added this to the 3.12.1 milestone Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant