[
https://issues.apache.org/jira/browse/KAFKA-9654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-9654.
------------------------------------
Fix Version/s: 2.5.1
2.4.2
Resolution: Fixed
> ReplicaAlterLogDirsThread can't be created again if the previous
> ReplicaAlterLogDirsThreadmeet encounters leader epoch error
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-9654
> URL: https://issues.apache.org/jira/browse/KAFKA-9654
> Project: Kafka
> Issue Type: Bug
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Priority: Critical
> Fix For: 2.4.2, 2.5.1
>
>
> ReplicaManager does create ReplicaAlterLogDirsThread only if an new future
> log is created. If the previous ReplicaAlterLogDirsThread encounters error
> when moving data, the target partition is moved to "failedPartitions" and
> ReplicaAlterLogDirsThread get idle due to empty partitions. The future log is
> still existent so we CAN'T either create another ReplicaAlterLogDirsThread to
> handle the parition or update the paritions of the idler
> ReplicaAlterLogDirsThread.
> ReplicaManager should call ReplicaAlterLogDirsManager#addFetcherForPartitions
> even if there is already a future log since we can create an new
> ReplicaAlterLogDirsThread to handle the new partitions or update the
> partitions of existent ReplicaAlterLogDirsThread to make it busy again.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
