You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrii Babiichuk (JIRA)" <ji...@apache.org> on 2015/05/12 16:53:59 UTC
[jira] [Commented] (AMBARI-11065) Make sure that KMS related
configs are updated when a new KMS is added to the cluster
[ https://issues.apache.org/jira/browse/AMBARI-11065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539963#comment-14539963 ]
Andrii Babiichuk commented on AMBARI-11065:
-------------------------------------------
+1 for the patch
> Make sure that KMS related configs are updated when a new KMS is added to the cluster
> -------------------------------------------------------------------------------------
>
> Key: AMBARI-11065
> URL: https://issues.apache.org/jira/browse/AMBARI-11065
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-11065.patch
>
>
> 2 configs to set are:
> * {{hadoop.security.key.provider.path}}
> * {{dfs.encryption.key.provider.uri}}
> Their value should be
> {noformat}
> kms://http@<keyserver_host>:<keyserver_port>/kms - For a single instance of KMS server
> kms://http@<keyserver_host>,<keyserver_host2>,<keyserver_host3>:<keyserver_port>/kms - For multiple instances of KMS servers (for HA)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)