<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Balancing kafka topics when new broker is added in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Balancing-kafka-topics-when-new-broker-is-added/m-p/175784#M77860</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/16846/brajeshreddy6.html" nodeid="16846"&gt;@Rajesh Reddy&lt;/A&gt;&lt;/P&gt;&lt;P&gt;
	Balancing data in kafka is not same as HDFS. You'd need to use partition re-assignment tool to move the partitions to new brokers.&lt;/P&gt;&lt;P&gt;Below is the detailed explanation from kafka &lt;A href="https://kafka.apache.org/0101/documentation.html#basic_ops_cluster_expansion"&gt;documentation&lt;/A&gt;: &lt;/P&gt;&lt;P&gt;
	&lt;EM&gt;Adding servers to a Kafka cluster is easy, just assign them a unique broker id and start up Kafka on your new servers. However these new servers will not automatically be assigned any data partitions, so unless partitions are moved to them they won't be doing any work until new topics are created. So usually when you add machines to your cluster you will want to migrate some existing data to these machines.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;
	The process of migrating data is manually initiated but fully automated. Under the covers what happens is that Kafka will add the new server as a follower of the partition it is migrating and allow it to fully replicate the existing data in that partition. When the new server has fully replicated the contents of this partition and joined the in-sync replica one of the existing replicas will delete their partition's data.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;
	The partition reassignment tool can be used to move partitions across brokers. An ideal partition distribution would ensure even data load and partition sizes across all brokers. The partition reassignment tool does not have the capability to automatically study the data distribution in a Kafka cluster and move partitions around to attain an even load distribution. As such, the admin has to figure out which topics or partitions should be moved around.&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 03 May 2018 00:29:34 GMT</pubDate>
    <dc:creator>sandyy006</dc:creator>
    <dc:date>2018-05-03T00:29:34Z</dc:date>
    <item>
      <title>Balancing kafka topics when new broker is added</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Balancing-kafka-topics-when-new-broker-is-added/m-p/175783#M77859</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We currently have 3 kafka brokers and about 250 topics. How do i re-balance the partitions and data when a new broker is added? Is running manual rebalance the only option? I was thinkin gof stopping a broker and then since we have 3 replications, it woul copy the topics in the stopped broker to new broker. Is that a good idea?&lt;/P&gt;</description>
      <pubDate>Thu, 03 May 2018 00:25:50 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Balancing-kafka-topics-when-new-broker-is-added/m-p/175783#M77859</guid>
      <dc:creator>brajeshreddy</dc:creator>
      <dc:date>2018-05-03T00:25:50Z</dc:date>
    </item>
    <item>
      <title>Re: Balancing kafka topics when new broker is added</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Balancing-kafka-topics-when-new-broker-is-added/m-p/175784#M77860</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/16846/brajeshreddy6.html" nodeid="16846"&gt;@Rajesh Reddy&lt;/A&gt;&lt;/P&gt;&lt;P&gt;
	Balancing data in kafka is not same as HDFS. You'd need to use partition re-assignment tool to move the partitions to new brokers.&lt;/P&gt;&lt;P&gt;Below is the detailed explanation from kafka &lt;A href="https://kafka.apache.org/0101/documentation.html#basic_ops_cluster_expansion"&gt;documentation&lt;/A&gt;: &lt;/P&gt;&lt;P&gt;
	&lt;EM&gt;Adding servers to a Kafka cluster is easy, just assign them a unique broker id and start up Kafka on your new servers. However these new servers will not automatically be assigned any data partitions, so unless partitions are moved to them they won't be doing any work until new topics are created. So usually when you add machines to your cluster you will want to migrate some existing data to these machines.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;
	The process of migrating data is manually initiated but fully automated. Under the covers what happens is that Kafka will add the new server as a follower of the partition it is migrating and allow it to fully replicate the existing data in that partition. When the new server has fully replicated the contents of this partition and joined the in-sync replica one of the existing replicas will delete their partition's data.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;
	The partition reassignment tool can be used to move partitions across brokers. An ideal partition distribution would ensure even data load and partition sizes across all brokers. The partition reassignment tool does not have the capability to automatically study the data distribution in a Kafka cluster and move partitions around to attain an even load distribution. As such, the admin has to figure out which topics or partitions should be moved around.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 03 May 2018 00:29:34 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Balancing-kafka-topics-when-new-broker-is-added/m-p/175784#M77860</guid>
      <dc:creator>sandyy006</dc:creator>
      <dc:date>2018-05-03T00:29:34Z</dc:date>
    </item>
    <item>
      <title>Re: Balancing kafka topics when new broker is added</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Balancing-kafka-topics-when-new-broker-is-added/m-p/175785#M77861</link>
      <description>&lt;P&gt;I recommend to trigger the manual rebalancing via kafka-reassign-partition.sh, not by bringing down one node. In most scenarios, when you bring down one node and bring it back on afterwards, it is also not considered for balancing. And you might cause other issues as well.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hortonworks.com/content/supportkb/150063/how-to-add-new-kafka-brokers-to-a-cluster-and-move.html" target="_blank"&gt;https://community.hortonworks.com/content/supportkb/150063/how-to-add-new-kafka-brokers-to-a-cluster-and-move.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 03 May 2018 00:42:34 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Balancing-kafka-topics-when-new-broker-is-added/m-p/175785#M77861</guid>
      <dc:creator>arald</dc:creator>
      <dc:date>2018-05-03T00:42:34Z</dc:date>
    </item>
    <item>
      <title>Re: Balancing kafka topics when new broker is added</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Balancing-kafka-topics-when-new-broker-is-added/m-p/175786#M77862</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/10159/snemuri.html" nodeid="10159"&gt;@Sandeep Nemuri&lt;/A&gt; would this be the same when i add additional dara directories to kafka?&lt;/P&gt;</description>
      <pubDate>Thu, 03 May 2018 00:50:34 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Balancing-kafka-topics-when-new-broker-is-added/m-p/175786#M77862</guid>
      <dc:creator>brajeshreddy</dc:creator>
      <dc:date>2018-05-03T00:50:34Z</dc:date>
    </item>
    <item>
      <title>Re: Balancing kafka topics when new broker is added</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Balancing-kafka-topics-when-new-broker-is-added/m-p/175787#M77863</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/16846/brajeshreddy6.html" nodeid="16846"&gt;@Rajesh Reddy&lt;/A&gt;&lt;P&gt;yes, the procedure would be same. As an alternative you can also look at : &lt;A href="https://community.hortonworks.com/content/supportkb/151087/how-to-move-kafka-partition-log-directory-within-a.html" target="_blank"&gt;https://community.hortonworks.com/content/supportkb/151087/how-to-move-kafka-partition-log-directory-within-a.html&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Thu, 03 May 2018 00:59:30 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Balancing-kafka-topics-when-new-broker-is-added/m-p/175787#M77863</guid>
      <dc:creator>sandyy006</dc:creator>
      <dc:date>2018-05-03T00:59:30Z</dc:date>
    </item>
    <item>
      <title>Re: Balancing kafka topics when new broker is added</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Balancing-kafka-topics-when-new-broker-is-added/m-p/175788#M77864</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/10159/snemuri.html" nodeid="10159"&gt;@Sandeep Nemuri&lt;/A&gt; That was helpful but what if i want to add additional disks rather than removing one and adding other??&lt;/P&gt;</description>
      <pubDate>Thu, 03 May 2018 01:51:24 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Balancing-kafka-topics-when-new-broker-is-added/m-p/175788#M77864</guid>
      <dc:creator>brajeshreddy</dc:creator>
      <dc:date>2018-05-03T01:51:24Z</dc:date>
    </item>
  </channel>
</rss>

