You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Sandor Molnar (JIRA)" <ji...@apache.org> on 2018/01/22 09:56:00 UTC
[jira] [Created] (AMBARI-22824) Yarn/MR2 should handle a customized
Zookeeper service principal name
Sandor Molnar created AMBARI-22824:
--------------------------------------
Summary: Yarn/MR2 should handle a customized Zookeeper service principal name
Key: AMBARI-22824
URL: https://issues.apache.org/jira/browse/AMBARI-22824
Project: Ambari
Issue Type: Improvement
Components: ambari-server
Affects Versions: 2.0.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 3.0.0
Yarn and MapReduce2 should handle a customized Zookeeper service principal name.
Currently this is not supported due to hardcoded and implicit values expecting the Zookeeper service principal name to be {{zookeeper/_HOST}} as opposed to something like {{zookeeper-mycluster/_HOST}}.
The following changes need to be made:
* common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py must be changed to not hardcode the Zookeeper principal name in
{code:java}
m_security_opts = format('-Dzookeeper.sasl.client=true -Dzookeeper.sasl.client.username=zookeeper -Djava.security.auth.login.config={yarn_jaas_file} -Dzookeeper.sasl.clientconfig=Client')
{code}
* {{-Dzookeeper.sasl.client.username=<ZOOKEEPER_PRINCPAL_NAME>}} should be added to {{YARN_OPTS}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)