You can keep the broker.id of the new node same as the old node. Then it
will start up and copy everything from the leader for the partitions it is
assigned to. After it is caught up, you can run thehttps://cwiki.apache.org/confluence/display/KAFKA/Replication+tools#Replicationtools-2.PreferredReplicaLeaderElectionTooltool
to balance the leaders, so that the new node will have a few leaders
and will start serving data.
On Mon, Dec 2, 2013 at 1:50 PM, Maxime Nay <[EMAIL PROTECTED]> wrote: