Add timeout option to some rabbitmqctl commands #61
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We decided to expend this in scope and list items (e.g. queues) that were unavailable or seem stuck. |
dcorbacho
pushed a commit
that referenced
this pull request
Nov 18, 2020
Prevent non-zero publisher count in Grafana when aggregating metrics
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our default (infinity) helps detect stuck processes but there should be a timeout option for operations convenience, see this rabbitmq-users thread for example.
We keep the default as is because historically, any picked value wasn't good enough because someone had a slow enough server.