Skip to content

Conversation

@kjnilsson
Copy link
Contributor

@kjnilsson kjnilsson commented Oct 19, 2022

Some systems may incur a substantial latency penalty when attempting reconnections to down nodes so to avoid this some stat related functions that gather info from all QQ member nodes now only try those nodes that are connected. This should help keeping things like the mgmt API functions and ctl commands a bit more responsive when RabbitMQ nodes are down.

Context: #6048

Some systems may incur a substantial latency penalty when attempting
reconnections to down nodes so to avoid this some stat related functions
that gather info from all QQ member nodes no only try those nodes
that are connected. This should help keeping things like the mgmt API
functions and ctl commands a bit more responsive.
@kjnilsson kjnilsson changed the title QQ: don't try to contact non-connected nodes for starts QQ: don't try to contact non-connected nodes for stats Oct 20, 2022
@kjnilsson kjnilsson marked this pull request as ready for review October 26, 2022 09:12
michaelklishin added a commit that referenced this pull request Oct 28, 2022
QQ: don't try to contact non-connected nodes for stats (backport #6183)
michaelklishin added a commit that referenced this pull request Oct 28, 2022
QQ: don't try to contact non-connected nodes for stats (backport #6183) (backport #6276)
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.

4 participants