Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # user >> Questions regarding broker


Copy link to this message
-
Re: Questions regarding broker
1 - no, unless broker4 is not the preferred leader. (The preferred
leader is the first broker in the assigned replica list). If a
non-preferred replica is the current leader you can run the
PreferredReplicaLeaderElection admin command to move the leader.
2 - The actual leader movement (on leader failover) is fairly low -
probably of the order of tens of ms. However, clients (producers,
consumers) may take longer to detect that (it needs to get back an
error response, handle an exception, issue a metadata request, get the
response to find the new leader, and all that can add up but it should
not be terribly high - I'm guessing on the order of a few hundred ms
to a second or so).
3 - That should work, although the admin command for adding more
partitions to a topic is currently being developed.
On Mon, Jul 8, 2013 at 11:02 PM, Calvin Lei <[EMAIL PROTECTED]> wrote:
> Hi,
>     I have two questions regarding the kafka broker setup.
>
> 1. Assuming i have a 4-broker and 2-zookeeper (running in quorum mode)
> setup, if topicA-partition0 has the leader set to broker4, can I change the
> leader to other broker without killing the current leader?
>
> 2. What is the latency of switching to a different leader when the current
> leader is down? Do we configure it using the consumer property -
> refresh.leader.backoff.ms
>
> 3. What is the best practice of dynamically adding a new node to a kafka
> cluster? Should i bring up the node, and then increase the replication
> factor for the existing topic(s)?
>
>
> thanks in advance,
> Cal