<?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: Kafka Rolling Upgrade in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Kafka-Rolling-Upgrade/m-p/132049#M94733</link>
    <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/36/lgeorge.html" nodeid="36"&gt;@lgeorge&lt;/A&gt;, fyi: the cluster is not kerberized.&lt;/P&gt;</description>
    <pubDate>Wed, 18 Jan 2017 12:49:30 GMT</pubDate>
    <dc:creator>chri</dc:creator>
    <dc:date>2017-01-18T12:49:30Z</dc:date>
    <item>
      <title>Kafka Rolling Upgrade</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Kafka-Rolling-Upgrade/m-p/132046#M94730</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We are planning the rolling upgrade from HDP 2.4.0.0 to 2.5.3.0. No downtime during the upgrade is especially crucial for the Kafka cluster:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Is the update of the Kafka brokers also rolling?&lt;/LI&gt;&lt;LI&gt;Will clients (producer and cusumer) from Kafka 0.9.0.2.4 releases work with brokers from Kafka 0.10.0 releases?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;If the answer for 1) and/or 2) is No - what is the best practice to guarantee no downtime?&lt;/P&gt;&lt;P&gt;Thank you in advance,
Christian&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jan 2017 20:22:01 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Kafka-Rolling-Upgrade/m-p/132046#M94730</guid>
      <dc:creator>chri</dc:creator>
      <dc:date>2017-01-17T20:22:01Z</dc:date>
    </item>
    <item>
      <title>Re: Kafka Rolling Upgrade</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Kafka-Rolling-Upgrade/m-p/132047#M94731</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/5386/christianguegi.html" nodeid="5386"&gt;@Christian Guegi&lt;/A&gt; I believe there are constraints for Kafka based on versions and on whether a cluster has Kerberos enabled or not. I'll try to find someone to respond for 2.4 to 2.5.3. &lt;/P&gt;</description>
      <pubDate>Wed, 18 Jan 2017 02:03:25 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Kafka-Rolling-Upgrade/m-p/132047#M94731</guid>
      <dc:creator>lgeorge</dc:creator>
      <dc:date>2017-01-18T02:03:25Z</dc:date>
    </item>
    <item>
      <title>Re: Kafka Rolling Upgrade</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Kafka-Rolling-Upgrade/m-p/132048#M94732</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/5386/christianguegi.html" nodeid="5386"&gt;@Christian Guegi&lt;/A&gt; You can go with manual upgrade of cluster and can upgrade kafka brokers one by one:&lt;/P&gt;&lt;P&gt;&lt;A href="http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.0/bk_command-line-upgrade/content/upgrade-kafka-23.html" target="_blank"&gt;http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.0/bk_command-line-upgrade/content/upgrade-kafka-23.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jan 2017 07:51:14 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Kafka-Rolling-Upgrade/m-p/132048#M94732</guid>
      <dc:creator>lraheja</dc:creator>
      <dc:date>2017-01-18T07:51:14Z</dc:date>
    </item>
    <item>
      <title>Re: Kafka Rolling Upgrade</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Kafka-Rolling-Upgrade/m-p/132049#M94733</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/36/lgeorge.html" nodeid="36"&gt;@lgeorge&lt;/A&gt;, fyi: the cluster is not kerberized.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jan 2017 12:49:30 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Kafka-Rolling-Upgrade/m-p/132049#M94733</guid>
      <dc:creator>chri</dc:creator>
      <dc:date>2017-01-18T12:49:30Z</dc:date>
    </item>
    <item>
      <title>Re: Kafka Rolling Upgrade</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Kafka-Rolling-Upgrade/m-p/132050#M94734</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/78/lraheja.html" nodeid="78"&gt;@lraheja&lt;/A&gt;, our HDP 2.4 cluster was installed with Ambari. Hence we must use &lt;STRONG&gt;&lt;A href="http://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-upgrade/content/index.html"&gt;Ambari Upgrade Guide&lt;/A&gt;&lt;/STRONG&gt; to perform the HDP 2.4 to HDP 2.5.0 upgrade. I don't think a manual upgrade is an option.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jan 2017 12:56:03 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Kafka-Rolling-Upgrade/m-p/132050#M94734</guid>
      <dc:creator>chri</dc:creator>
      <dc:date>2017-01-18T12:56:03Z</dc:date>
    </item>
    <item>
      <title>Re: Kafka Rolling Upgrade</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Kafka-Rolling-Upgrade/m-p/132051#M94735</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/5386/christianguegi.html" nodeid="5386"&gt;@Christian Guegi&lt;/A&gt; &lt;/P&gt;&lt;P&gt;You can do the rolling upgrade without impacting downtime. Before starting the upgrade add these two properties to kafka config. You can add the below configs via ambari -&amp;gt; kafka -&amp;gt; Advanced custom properties.&lt;/P&gt;&lt;P&gt;1. inter.broker.protocol.version = 0.9.0 ( HDP 2.4 kafka version)&lt;/P&gt;&lt;P&gt;2. log.message.format.version = 0.9.0&lt;/P&gt;&lt;P&gt;once these properties are set you can upgrade one broker at a time. Once the broker upgraded and made it into ISR move onto next one to minimize any downtime clients might see.&lt;/P&gt;&lt;P&gt;Once the upgrade finished you can remove inter.broker.protocol.version .&lt;/P&gt;&lt;P&gt;Once you upgrade the clients to kafka_clients 0.10.0.1 version you can remove the log.message.format.version as well.&lt;/P&gt;&lt;P&gt;More details are on this page &lt;A href="https://kafka.apache.org/0100/documentation.html#upgrade" target="_blank"&gt;https://kafka.apache.org/0100/documentation.html#upgrade&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jan 2017 13:43:43 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Kafka-Rolling-Upgrade/m-p/132051#M94735</guid>
      <dc:creator>schintalapani</dc:creator>
      <dc:date>2017-01-18T13:43:43Z</dc:date>
    </item>
    <item>
      <title>Re: Kafka Rolling Upgrade</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Kafka-Rolling-Upgrade/m-p/132052#M94736</link>
      <description>&lt;P&gt;FYI: With above description we were able to upgrade to version 2.5.3 without any Kafka cluster downtime. We only had some issues with a Kafka client written in Go.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 22:27:03 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Kafka-Rolling-Upgrade/m-p/132052#M94736</guid>
      <dc:creator>chri</dc:creator>
      <dc:date>2017-03-08T22:27:03Z</dc:date>
    </item>
  </channel>
</rss>

