David Arthur created KAFKA-15968:
------------------------------------
Summary: QuorumController does not treat CorruptRecordException as
fatal
Key: KAFKA-15968
URL: https://issues.apache.org/jira/browse/KAFKA-15968
Project: Kafka
Issue Type: Bug
Affects Versions: 3.6.0, 3.7.0
Reporter: David Arthur
When QuorumController encounters a CorruptRecordException, it does not include
the exception in the log message. Since CorruptRecordException extends
ApiException, it gets caught by the first condition in
EventHandlerExceptionInfo#fromInternal.
The controller treats ApiException as an excepted case (for things like authz
errors of creating a topic that already exists) so it does not cause a
failover. If the active controller sees a corrupt record, it should be a fatal
error.
While we are fixing this, we should audit the subclasses of ApiException and
make sure we are handling the fatal ones correctly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
