Issue120 - report broker side queue size. #122
Closed
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
also messageRateMax implemented for consumer.
petersilva
requested review from
reidsunderland,
MagikEh,
tysonkaufmann and
andreleblanc11
petersilva
added
the
different_from_python
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.
closes #120
Implementation to match python... MetPX/sarracenia#767
Also implemented messageRateMax on the consumer side, trying to catch messages
in the broker side queue. It turns out that C setting are such that it greedily ingests
all messages regardless of queue settings, so the broker side queue are always empty.
see #121 for details.
It works, but the metrics are always zero as a result.