You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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:
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.
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.
The text was updated successfully, but these errors were encountered: