Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
MIME-Version: 1.0
In-Reply-To: <CAMd5YszdGhUQCJNe1mE9+6vDMqe=KbLtyyTgEvFjj_aJqQzuXw@mail.gmail.com>
References: <CAMd5YszdGhUQCJNe1mE9+6vDMqe=KbLtyyTgEvFjj_aJqQzuXw@mail.gmail.com>
From: Tom Bentley <t.j.bentley@gmail.com>
Date: Mon, 7 Aug 2017 16:21:53 +0100
Message-ID: <CAMd5YsyFL4KuWHV8b7cZ_mMvjNjeJEHdXAaHB7JF6VVSEV4fqA@mail.gmail.com>
Subject: Re: [DISCUSS] KIP-183 - Change PreferredReplicaLeaderElectionCommand
 to use AdminClient
To: dev@kafka.apache.org
Content-Type: multipart/alternative; boundary="001a113fd7422451f405562b68da"
archived-at: Mon, 07 Aug 2017 15:22:02 -0000

--001a113fd7422451f405562b68da
Content-Type: text/plain; charset="UTF-8"

Hi,

I've updated this KIP slightly, to clarify a couple of points.

One thing in particular that I would like feedback on is what authorization
should be required for triggering the election of the preferred leader?

Another thing would be whether the request and responses should be grouped
by topic name. This would make for smaller messages when triggering
elections for multiple partitions of the same topic.

I'd be grateful for any feedback you may have.

Cheers,

Tom

On 2 August 2017 at 18:34, Tom Bentley <t.j.bentley@gmail.com> wrote:

> In a similar vein to KIP-179 I've created KIP-183 (
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-183+-+Change+
> PreferredReplicaLeaderElectionCommand+to+use+AdminClient) which is about
> deprecating the --zookeeper option to kafka-preferred-replica-election.sh
> and replacing it with an option which would use a new AdminClient-based API.
>
> As it stands the KIP is focussed on simply moving the existing
> functionality behind the AdminClient.
>
> I'd be grateful for any feedback people may have on this.
>
> Thanks,
>
> Tom
>

--001a113fd7422451f405562b68da--