Created 01-17-2017 12:22 PM
Hi,
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:
If the answer for 1) and/or 2) is No - what is the best practice to guarantee no downtime?
Thank you in advance, Christian
Created 01-18-2017 05:43 AM
Want to get a detailed solution you have to login/registered on the community
Register/LoginCreated 01-17-2017 06:03 PM
@Christian Guegi 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.
Created 01-18-2017 04:49 AM
Hi @lgeorge, fyi: the cluster is not kerberized.
Created 01-17-2017 11:51 PM
@Christian Guegi You can go with manual upgrade of cluster and can upgrade kafka brokers one by one:
Created 01-18-2017 04:56 AM
Hi @lraheja, our HDP 2.4 cluster was installed with Ambari. Hence we must use Ambari Upgrade Guide to perform the HDP 2.4 to HDP 2.5.0 upgrade. I don't think a manual upgrade is an option.
Created 01-18-2017 05:43 AM
Want to get a detailed solution you have to login/registered on the community
Register/LoginCreated 03-08-2017 02:27 PM
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.