Re: Unexpected Rebalances ，Any tips on APIs or debug techniques to figure out rebalance causes?

Rebalancing happens mainly because of these reasons: You restart consumer Consumer host is not reachable You stop consumer All above situations are fine when you have sufficient number of consumers(threads) to read from the available partitions and all consumers are logically distributed across m

Re: How to deal with the Error: KAFKA_STORAGE_ERROR

Hi Peter, Firstly, I'd check disk health, then I'd check owners and permissions on files in your log dir, eliminate those as issues. Secondly, are you tracking metrics on offline log dirs? Cheers, Liam On Thu, 28 Apr 2022 at 15:55, Dong, Peter A. (NSB - CN/Qingdao) < peter.a.d...@nokia-sbell.co

RE: How to deal with the Error: KAFKA_STORAGE_ERROR

Liam, Thanks a lot for your help. I have not made metrics yet. I have just checked everything about file privileges again, all correct. Then I notice there's an error in state-change log as below, [2022-04-26 19:07:17,727] ERROR [Broker id=1] Topic ID in memory: 7LRTCKIRT5W5qZUrLQ_0wA does n

Re: Unexpected loss of Offsets

Luke, Do you know if 2.8.2 will be released anytime soon? It appears to be waiting on https://issues.apache.org/jira/browse/KAFKA-13805 for which fixes are available. Regards, James. On 11/04/2022, at 14:22, Luke Chen mailto:show...@gmail.com>> wrote: Hi James, This looks like this known i

Re: Unexpected loss of Offsets

Hi James, So far, v2.8.2 is not planned, yet. And usually, the patch release only has one, that is, v2.8.0, and v2.8.1. But there are of course some exceptions that some releases have 2 or 3 patch releases. For KAFKA-13658, you can check KAFKA-13658

Re: Unexpected loss of Offsets

Luke, I would argue that https://issues.apache.org/jira/browse/KAFKA-13636 is a critical defect as it can have a very serious impact. We run on AWS MSK which supports these versions: https://docs.aws.amazon.com/msk/latest/developerguide/supported-kafka-versions.html. We are currently on 2.7.2