You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2016/03/16 15:18:33 UTC
[jira] [Commented] (AMBARI-15439) Add Upgrade Check for Kafka Kerb
on HDP 2.2 -> 2.3+
[ https://issues.apache.org/jira/browse/AMBARI-15439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197378#comment-15197378 ]
Dmytro Sen commented on AMBARI-15439:
-------------------------------------
Unit tests passed locally
{code}
[10:27:48][Step 1/1] [INFO] Reactor Summary:
[10:27:48][Step 1/1] [INFO]
[10:27:48][Step 1/1] [INFO] Ambari Views ...................................... SUCCESS [2.687s]
[10:27:48][Step 1/1] [INFO] Ambari Metrics Common ............................. SUCCESS [2.131s]
[10:27:48][Step 1/1] [INFO] Ambari Server ..................................... SUCCESS [53:34.339s]
[10:27:48][Step 1/1] [INFO] ------------------------------------------------------------------------
[10:27:48][Step 1/1] [INFO] BUILD SUCCESS
[10:27:48][Step 1/1] [INFO] ------------------------------------------------------------------------
[10:27:48][Step 1/1] [INFO] Total time: 53:39.950s
[10:27:48][Step 1/1] [INFO] Finished at: Wed Mar 16 10:27:48 UTC 2016
[10:27:48][Step 1/1] [INFO] Final Memory: 65M/983M
[10:27:48][Step 1/1] [INFO] ------------------------------------------------------------------------
{code}
> 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
> Assignee: Dmytro Sen
> 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)