vamossagar12 commented on PR #13504: URL: https://github.com/apache/kafka/pull/13504#issuecomment-1565417056
@dengziming , I am looping you in here since I see you wrote the Admin APIs that this PR is trying to use and need your inputs for this PR. This is the description of the problem at hand : ``` Currently, the WorkerSinkTask fails when a subscribed topic is deleted and the RebalanceListener tries to fetch the position of such a topic. Note that this doesn't happen whenever a topic is deleted but instead under extreme scenarios like mass deletion of topics. To get around this, Admin Client has been added to WorkerSinkTask. When RebalanceListener is invoked, and a TimeoutException is thrown upon fetching position, it is checked if the topic exists. If it doesn't, then the offset of that TopicPartition isn't committed and the deleted topic name is cached so that any future position fetch for other partitions of the deleted topic doesn't invoke AdminClient again. ``` This PR tries to ascertain that the topic has already been deleted using the Admin API describeTopic. However, none of us here have the expertise on the clients side of things. More specifically => 1) Is the approach taken in this PR even a viable one? 2) More importantly, is this something that should be fixed on the Clients side of things? If yes, I can create a JIRA ticket for clients and take a call if we need an interim fix for this meanwhile it gets fixed? Plz let me know. -- 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: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
