Display Topic and Broker Sizes #146
Merged
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
|
Can you rebase or merge master? |
|
@patelh rebased it |
|
Should I merge or did you want to add the option to enable/disable consumer offset ? |
|
Could you merge it? I'd like to have enable/disable consumer offset as a On Tue, Nov 24, 2015 at 2:21 PM, patelh notifications@github.com wrote:
|
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.
Added an option to display topic and broker sizes.
This works only after patch https://issues.apache.org/jira/browse/KAFKA-1614 is applied to Kafka.
Longer broker-view-update-seconds is recommended since BVActor queries sizes for all existing segments. I am currently using a version that doesn't fetch consumer data, but with consumer data getting fetched, Kafka Manager might be overloaded. So I plan to make fetching consumer data configurable.