[AMBARI-23070] Yarn Registry DNS is not added in Stale Component restart when yarn-env.sh is modified

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.7.0
• Assignee: Unassigned
• Reporter: Yesha Vora
• Created: 23/Feb/18 23:10
• Updated: 23/Feb/18 23:10

Description

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

1) Update yarn-env.sh

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 %}

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.