You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Velmurugan Periasamy (JIRA)" <ji...@apache.org> on 2015/07/02 00:23:04 UTC
[jira] [Commented] (AMBARI-12247) Ranger Plugin SSL configuration
for YARN needs to be fixed to not clash with HDFS
[ https://issues.apache.org/jira/browse/AMBARI-12247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611093#comment-14611093 ]
Velmurugan Periasamy commented on AMBARI-12247:
-----------------------------------------------
Review request available here - https://reviews.apache.org/r/36111/
> Ranger Plugin SSL configuration for YARN needs to be fixed to not clash with HDFS
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-12247
> URL: https://issues.apache.org/jira/browse/AMBARI-12247
> Project: Ambari
> Issue Type: Bug
> Reporter: Velmurugan Periasamy
> Assignee: Velmurugan Periasamy
> Priority: Critical
>
> When enabling SSL for Ranger, Yarn plugin communication breaks due to the below two issues.
> 1] Ambari code generates ranger-policymgr-ssl.xml for both HDFS and Yarn. Need to generate different config file name for each service (because NameNode and ResourceManager can be running on the same host)
> 2] In yarn config (Advanced ranger-yarn-security), ranger.plugin.yarn.policy.rest.ssl.config.file attribute needs to be set as /etc/hadoop/conf/ranger-policymgr-ssl-yarn.xml => Currently, it is using the default value /etc/yarn/conf/ranger-policymgr-ssl.xml which is incorrect
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)