Skip to content
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

invalid partition number increased everytime after intra-broker disk re-balance #845

Open
linehrr opened this issue Jul 18, 2019 · 4 comments
Labels
correctness A condition affecting the proper functionality.

Comments

@linehrr
Copy link
Contributor

linehrr commented Jul 18, 2019

Screen Shot 2019-07-18 at 2 50 57 PM

there is no useful logs from either CC or broker's metric collector.
anyone knows what would be the possible cause?

Update:
after we restarted some brokers, we are getting back all partitions as valid. therefore it's indicating that some brokers stopped sending metrics. During intra-broker rebalancing, there were some brokers failed due to timeout on logdir meta data fetching, and therefore stuck at moving internal log dirs. we did the manual reassignment to fix them but those brokers seem to stop sending metric afterwards, until we restarted them.

@linehrr linehrr changed the title invalid partition number increased everytime after intro broker disk re-balance invalid partition number increased everytime after intra-broker disk re-balance Jul 19, 2019
@efeg efeg added the correctness A condition affecting the proper functionality. label Jul 25, 2019
@efeg
Copy link
Collaborator

efeg commented Jun 10, 2020

@linehrr Does this issue still happen?

@linehrr
Copy link
Contributor Author

linehrr commented Jun 10, 2020

We haven’t tested it against the newest Kafka version. But the old version 1.1 it is still happening.

@jrevillard
Copy link
Contributor

jrevillard commented Feb 26, 2021

Dear @linehrr , @efeg does it means that there is no way to detect that some broker does not send metrics currently ?

I'm asking because in my test cluster, I see also this info:

image

And I was just trying to figure out what could be the problem... In fact we do not know what are the problematic partitions and to which topic/broker they belong to.

Best.

@jrevillard
Copy link
Contributor

As far as I'm concerned, brokers restart does not help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
correctness A condition affecting the proper functionality.
Projects
None yet
Development

No branches or pull requests

3 participants