kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jun Rao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5473) handle ZK session expiration properly when a new session can't be established
Date Tue, 07 Nov 2017 01:04:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241272#comment-16241272
] 

Jun Rao commented on KAFKA-5473:
--------------------------------

[~prasincs], thanks. I think the existing zk state metric is probably enough. If a new Zookeeper
object can't be created, the ZK state will remain in the CLOSED state. So, the admin can monitor
and set up an alert on this.

When do you think you can have the patch ready? We want to complete this jira relatively soon
so that we can migrate off the old zkClient.

> handle ZK session expiration properly when a new session can't be established
> -----------------------------------------------------------------------------
>
>                 Key: KAFKA-5473
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5473
>             Project: Kafka
>          Issue Type: Sub-task
>    Affects Versions: 0.9.0.0
>            Reporter: Jun Rao
>            Assignee: Prasanna Gautam
>             Fix For: 1.1.0
>
>
> In https://issues.apache.org/jira/browse/KAFKA-2405, we change the logic in handling
ZK session expiration a bit. If a new ZK session can't be established after session expiration,
we just log an error and continue. However, this can leave the broker in a bad state since
it's up, but not registered from the controller's perspective. Replicas on this broker may
never to be in sync.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message