[
https://issues.apache.org/jira/browse/KAFKA-12751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17414212#comment-17414212
]
Rajini Sivaram commented on KAFKA-12751:
----------------------------------------
The bug only happens in an unusual case where the proposed ISR is the same as
the expected ISR and the chances of hitting that are very low. And it is an
issue only if `inter.broker.protocol.version >= 2.7`. If it does occur, further
ISR updates don't occur, so the broker will need to be restarted. Release plan
for 2.8.1 is here:
[https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+2.8.1,] work is
under way and the release is expected in within the next few weeks.
> ISRs remain in in-flight state if proposed state is same as actual state
> ------------------------------------------------------------------------
>
> Key: KAFKA-12751
> URL: https://issues.apache.org/jira/browse/KAFKA-12751
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 2.7.0, 2.8.0, 2.7.1
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
> Priority: Critical
> Fix For: 2.7.2, 2.8.1
>
>
> If proposed ISR state in an AlterIsr request is the same as the actual state,
> Controller returns a successful response without performing any updates. But
> the broker code that processes the response leaves the ISR state in in-flight
> state without committing. This prevents further ISR updates until the next
> leader election.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
