Colin Kuo
Colin Kuo
> If we enable PC and reuse the existing consumer group, is that possible to avoid the error, such as `Unexpected magic: 2`. To create a new consumer group will...
> Thanks for the quick response @astubbs Yes, we wanted to explore whether we can reuse the same offsets. I'd consider that It's similar to a new completely different Kafka...
When you say to add an option for it to be ignored, does it mean the we don't see the error once we turn the option on. Also, PC will...
> > we don't see the error once we turn the option o > > yes, just a warning. and it'll only show the first time, going forward it wouldn't...
https://developer.confluent.io/courses/kafka-streams/hands-on-error-handling/ Borrowing the idea from `ProductionExceptionHandler` of Kafka Streams also looks good. Just let users to decide either fail the processing or ignore the problematic messages
Hi, @astubbs. We are experiencing this issue now with version 0.5.2.3. When this happened, no messages were consumed from the assigned partition like what @bartman64 encountered previously. Furthermore, it's relatively...
Hi, @astubbs When the error was spamming the logs, the CPU usage of the pods was low, and the offsets of assigned partitions were not moving fast enough. The outcome...
Hi @rkolesnev We are starting to test 5.0.2.7 and will keep you posted if any updates. Thanks!
@rkolesnev We have seen the same error with version **0.5.2.7**. `Truncating state - removing records lower than 55674910 from partition 34 of topic data.input.topic Offsets have been removed from the...