You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Niket Goel (Jira)" <ji...@apache.org> on 2022/10/11 16:57:00 UTC
[jira] [Resolved] (KAFKA-14275) KRaft Controllers should crash after failing to apply any metadata record
[ https://issues.apache.org/jira/browse/KAFKA-14275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niket Goel resolved KAFKA-14275.
--------------------------------
Fix Version/s: 3.3
Reviewer: Jason Gustafson
Resolution: Fixed
> KRaft Controllers should crash after failing to apply any metadata record
> --------------------------------------------------------------------------
>
> Key: KAFKA-14275
> URL: https://issues.apache.org/jira/browse/KAFKA-14275
> Project: Kafka
> Issue Type: Bug
> Components: kraft
> Affects Versions: 3.3.1
> Reporter: Niket Goel
> Assignee: Niket Goel
> Priority: Major
> Fix For: 3.3
>
>
> When replaying records on a standby controller, any error encountered will halt further processing of that batch. Currently we log an error and allow the controller to continue normal operation. In contrast a similar error on the active controller causes it to halt and exit the jvm. This is inconsistent behavior as nothing prevents a standby from eventually becoming the active controller (even when it had skipped over a record batch). We should halt the process in the case of a standby controller as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)