[ https://issues.apache.org/jira/browse/AMBARI-15439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmytro Grinenko updated AMBARI-15439: ------------------------------------- Attachment: AMBARI-15439.patch.1 > Add Upgrade Check for Kafka Kerb on HDP 2.2 -> 2.3+ > --------------------------------------------------- > > Key: AMBARI-15439 > URL: https://issues.apache.org/jira/browse/AMBARI-15439 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: trunk, 2.2.2 > Reporter: Dmytro Grinenko > Priority: Critical > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15439.patch, AMBARI-15439.patch.1 > > > Users that are running HDP 2.2 with Kafka and Kerberos is enabled, Kafka does > is not kerberized (because Kafka in HDP 2.2 did not support Kerb). > In HDP 2.3, Kafka supports Kerb. > Therefore, when that HDP 2.2 user upgrades to HDP 2.3, their Kafka will get > Kerberized unintentionally. > We need to an a pre-upgrade check to warn the user this will happen. > - If cluster is HDP 2.2 > - If kerberos is enabled > - If cluster is kerb'd > - If target upgrade is to HDP 2.3 (or later) > - Warning for both EU and RU upgrades > It's a warning check, not a required check. Should inform the user that since > their cluster has Kerberos enabled, after upgrade, Kafka will be Kerberized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)