Re: [PR] KAFKA-15968 Handle two specific ApiExceptions in EventHandlerExceptionInfo [kafka]
github-actions[bot] commented on PR #14919: URL: https://github.com/apache/kafka/pull/14919#issuecomment-1975645879 This PR is being marked as stale since it has not had any activity in 90 days. If you would like to keep this PR alive, please ask a committer for review. If the PR has merge conflicts, please update it with the latest from trunk (or appropriate release branch) If this PR is no longer valid or desired, please feel free to close it. If no activity occurs in the next 30 days, it will be automatically closed. -- 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
[PR] KAFKA-15968 Handle two specific ApiExceptions in EventHandlerExceptionInfo [kafka]
mumrah opened a new pull request, #14919: URL: https://github.com/apache/kafka/pull/14919 This patch adds two cases to EventHandlerExceptionInfo for exceptions thrown by the log layer. Prior to this change, the log could throw a CorruptRecordException and the QuorumController would not treat it as a fatal exception. E.g., ``` INFO [ControllerServer id=9990] handleCommit[baseOffset=192554233]: event failed with CorruptRecordException in 234 microseconds. ``` -- 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
