dajac commented on PR #14557: URL: https://github.com/apache/kafka/pull/14557#issuecomment-1864471696
> * [KAFKA-16033](https://issues.apache.org/jira/browse/KAFKA-16033): To review the retry logic, considering moving it to the callers. This definitely aligns with the legacy coordinator approach, and would make the intentions clearer, but when considering it before seemed that it would lead to duplicated retry logic in callers that require similar retry, and seemed better to have the CommitMgr as single responsible of the retry logic based on the intention (params) of the caller. That was what led to the current approach, but I do get the trade-off, so I will take the 2 tasks in sync, attempt to unify/centralize the error handling in the commitMgr first, and re-evaluate the retry logic placement. Thanks @lianetm. I think that we could still keep the error handling in the commit manager. One way would be to have multiple entry points (commitSync, commitAsync, autoCommitAsync, etc.) in the manager and they could do the right thing when the future is completed. -- 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
