yashmayya commented on PR #13530: URL: https://github.com/apache/kafka/pull/13530#issuecomment-1581192139
> Modifying the status parts of the REST API seems less like introducing further divergence and more like honestly reporting that existing divergence to users. Fair enough, I've pushed a change (which is oddly not showing up on the GitHub PR UI, although it does show up on my fork's branch which this PR is created from) where the connector's status is updated to failed and added some tests. I'm wondering whether we should also add some verbiage like `If there were any tasks running previously, they will continue running` to make it clear to users that it's only the connector instance that has failed as a result of not being able to reconfigure its tasks on startup (either first time or post update) / restart / resume. > Regardless, you're correct that we can't really alter the infinite-retry logic in distributed mode without a KIP. I do think a long-term fix for this problem would involve aligning how the two modes handle this kind of failure. Would love to see that if you have the time 😄 I'll add it to my TODO list if you think it's worth fixing 😄 -- 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]
