You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Tom Bentley (Jira)" <ji...@apache.org> on 2020/03/20 07:59:00 UTC

[jira] [Assigned] (KAFKA-9737) Describing log dir reassignment times out if broker is offline

     [ https://issues.apache.org/jira/browse/KAFKA-9737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Bentley reassigned KAFKA-9737:
----------------------------------

    Assignee: Tom Bentley

> Describing log dir reassignment times out if broker is offline
> --------------------------------------------------------------
>
>                 Key: KAFKA-9737
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9737
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jason Gustafson
>            Assignee: Tom Bentley
>            Priority: Major
>
> If there is any broker offline when trying to describe a log dir reassignment, then we get the something like the following error:
> {code}
> Status of partition reassignment:                                                                                                                                                      Partitions reassignment failed due to org.apache.kafka.common.errors.TimeoutException: Call(callName=describeReplicaLogDirs, deadlineMs=1584663960068, tries=1, nextAllowedTryMs=158466
> 3960173) timed out at 1584663960073 after 1 attempt(s)                                                                                                                         
> java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TimeoutException: Call(callName=describeReplicaLogDirs, deadlineMs=1584663960068, tries=1, nextAllowedTryMs=158
> 4663960173) timed out at 1584663960073 after 1 attempt(s)                                                                                                                     
>         at org.apache.kafka.common.internals.KafkaFutureImpl.wrapAndThrow(KafkaFutureImpl.java:45)                                                                                     
>         at org.apache.kafka.common.internals.KafkaFutureImpl.access$000(KafkaFutureImpl.java:32)                                                                               
>         at org.apache.kafka.common.internals.KafkaFutureImpl$SingleWaiter.await(KafkaFutureImpl.java:89)                                                                               
>         at org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:260)                                                                                    
>         at kafka.admin.ReassignPartitionsCommand$.checkIfReplicaReassignmentSucceeded(ReassignPartitionsCommand.scala:381)                                                           
>         at kafka.admin.ReassignPartitionsCommand$.verifyAssignment(ReassignPartitionsCommand.scala:98)                                                                         
>         at kafka.admin.ReassignPartitionsCommand$.verifyAssignment(ReassignPartitionsCommand.scala:90)
>         at kafka.admin.ReassignPartitionsCommand$.main(ReassignPartitionsCommand.scala:61)
>         at kafka.admin.ReassignPartitionsCommand.main(ReassignPartitionsCommand.scala)
> Caused by: org.apache.kafka.common.errors.TimeoutException: Call(callName=describeReplicaLogDirs, deadlineMs=1584663960068, tries=1, nextAllowedTryMs=1584663960173) timed out at 15846
> 63960073 after 1 attempt(s)
> Caused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment.
> {code}
> It would be nice if the tool was smart enough to notice brokers that are offline and report them as such while reporting the status of reassignments for online brokers.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)