[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223232#comment-16223232
]
Prasanna Gautam edited comment on KAFKA-5473 at 10/28/17 4:42 AM:
------------------------------------------------------------------
Thanks [~junrao], looks like a good start.- Is there plan for a way to get
notified via a metric or state change when kafka gets in this state? I think it
would be useful to know how often the cluster is getting in that state and
trigger alerts. - I missed the ZKSessionState being set to RECONNECTING on
first read.
was (Author: prasincs):
Thanks [~junrao], looks like a good start. Is there plan for a way to get
notified via a metric or state change when kafka gets in this state? I think it
would be useful to know how often the cluster is getting in that state and
trigger alerts.
> 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)
