Skip to content

Improve stream reader metrics cleanup (backport #3340) #3354

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

Merged
merged 8 commits into from
Sep 1, 2021

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Sep 1, 2021

This is an automatic backport of pull request #3340 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.io/

gerhard and others added 8 commits September 1, 2021 02:09
Otherwise metrics will not get cleaned up correctly when processes crash.

It's also tidier to do this in a single place, in terminate/3

Pair: @kjnilsson

Signed-off-by: Gerhard Lazu <[email protected]>
(cherry picked from commit dad0025)
Pair: @kjnilsson

Signed-off-by: Gerhard Lazu <[email protected]>
(cherry picked from commit 0ecf3d4)
Pair: @kjnilsson

Signed-off-by: Gerhard Lazu <[email protected]>
(cherry picked from commit 6c0ba03)
This ensures that only nodes that are ready to host stream members
are included in the election. This avoids continuous restart attempts
when the rabbit application is stopped.

(cherry picked from commit 9092de1)
Some logs used ~p to format a full stack trace. Given these warnings are emitted during
any nodedown this unnecessarily pollutes the logs. Trimmed using ~W instead.

(cherry picked from commit b59d87d)
Also increased the tick timeout to avoid checking for new rabbit nodes
to auto add too often.

Also increased sleep times for nodedowns to retry less often.

(cherry picked from commit c016567)
When the server initiate connection close.

(cherry picked from commit c240ec2)
Rather than sleeping for 6 seconds, we want to check that replica
recovered multiple times within 30 seconds, and either eventually
succeed, or fail if this does not recover within 30 seconds, the default
await_condition time interval.

Pair: @kjnilsson

Signed-off-by: Gerhard Lazu <[email protected]>
(cherry picked from commit 6a1faa6)
@michaelklishin michaelklishin merged commit 9863226 into v3.9.x Sep 1, 2021
@michaelklishin michaelklishin deleted the mergify/bp/v3.9.x/pr-3340 branch September 1, 2021 03:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants