kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Onur Karaman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-6146) re-register the exist watch on PreferredReplicaElectionZNode after the preferred leader election completes
Date Tue, 07 Nov 2017 21:13:00 GMT

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

Onur Karaman updated KAFKA-6146:
--------------------------------
    Description: We currently enqueue a PreferredReplicaLeaderElection controller event in
PreferredReplicaElectionHandler's handleCreation, handleDeletion, and handleDataChange. We
really only need to enqueue the event and re-register the exist watch on after preferred replica
leader election completes.  (was: Currently, after the PreferredReplicaElectionZNode is removed,
we don't register the exist watcher on the path again. This means that future preferred replica
election event will be missed.)

> re-register the exist watch on PreferredReplicaElectionZNode after the preferred leader
election completes 
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-6146
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6146
>             Project: Kafka
>          Issue Type: Sub-task
>    Affects Versions: 1.1.0
>            Reporter: Jun Rao
>             Fix For: 1.1.0
>
>
> We currently enqueue a PreferredReplicaLeaderElection controller event in PreferredReplicaElectionHandler's
handleCreation, handleDeletion, and handleDataChange. We really only need to enqueue the event
and re-register the exist watch on after preferred replica leader election completes.



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

Mime
View raw message