Yesha Vora created AMBARI-23070:
-----------------------------------

             Summary: Yarn Registry DNS is not added in Stale Component restart 
when yarn-env.sh is modified    
                 Key: AMBARI-23070
                 URL: https://issues.apache.org/jira/browse/AMBARI-23070
             Project: Ambari
          Issue Type: Bug
    Affects Versions: 2.7.0
            Reporter: Yesha Vora


Scenario:
Create a secure Hdp 3 cluster. Yarn DNS server was stopped.

1) Update yarn-env.sh
{code:java|title=example add below block to yarn-env.sh}
{% if security_enabled %}
export 
YARN_REGISTRYDNS_OPTS="-Djava.security.auth.login.config={{yarn_ats_jaas_file}}"
{% endif %}{code}
2) Click on Restart stale components

Here, Yarn DNS registry component is not restarted. Only Resourcemanager, 
nodemanagers. TimelineServer, TimelineReader v.2 are restarted.

Yarn DNS registry server should be restarted by stale component restart.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to