You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Onur Karaman (JIRA)" <ji...@apache.org> on 2017/11/07 21:32:00 UTC

[jira] [Updated] (KAFKA-6146) minimize the number of triggers enqueuing PreferredReplicaLeaderElection events

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

Onur Karaman updated KAFKA-6146:
--------------------------------
    Summary: minimize the number of triggers enqueuing PreferredReplicaLeaderElection events  (was: re-register the exist watch on PreferredReplicaElectionZNode only after the preferred leader election completes )

> minimize the number of triggers enqueuing PreferredReplicaLeaderElection events
> -------------------------------------------------------------------------------
>
>                 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 PreferredReplicaElectionZNode after preferred replica leader election completes.



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