FrankChen021 commented on issue #12385: URL: https://github.com/apache/druid/issues/12385#issuecomment-1098650805
Oh, you're right. I took the single replica as single partition. The 'reset' operation is supposed to delete the partition information from the metadata storage, and then restart the kafka consumer. If a normal Kafka consumer can consume the messages from the reset partitions, I think Druid's consumer can consume too. Because Druid also uses the high level APIs on `KafkaConsumer` to pull messages. The only difference between a Druid's consumer and tranditional use of KafkaConsumer is that Druid does not call `commit` method to commit the consumed offset back to Kafka cluster but only store it in Druid's own metadata store. Since this problem occurs on your environment, could you check: 1. if the metadata is cleared after the 'reset' operation 2. the logs of overlord after the 'reset' opreation to see any warning or errors. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
