Skip to main content
dch44
dch44
Silver ⭐️⭐️
March 31, 2023
Solved

Error while upgrading to HDP-7.1.7

We are upgrading our cluster from HDP 2.6.5 to HDP-7.1.70 :

During the upgrading process ( about 65 %), it fails to restart the mapreduce/historyserver with the below error.

Unable to find a solution

Any idea or help ?

 

raceback (most recent call last):
File "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/historyserver.py", line 126, in <module>
HistoryServer().execute()
File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 352, in execute
method(env)
File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 987, in restart
self.stop(env, upgrade_type=upgrade_type)
File "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/historyserver.py", line 47, in stop
import params
File "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/params.py", line 29, in <module>
from params_linux import *
File "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/params_linux.py", line 374, in <module>
yarn_registry_dns_principal_name = yarn_registry_dns_principal_name.replace('_HOST', hostname.lower())
File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py", line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found in configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter 'yarn.registry-dns.principal' was not found in configurations dictionary!


upgrade_hdp7_error_mr.JPG
akhilsnaik
akhilsnaikAnswer
Gold ⭐️⭐️⭐️
April 3, 2023

so it looks like Ambari is looking for an Configuration : yarn.registry-dns.principal and its missing in Configuration.

Can you see adding to yarn-env in Yarn Services configuration helps ? 

 

For ex , you can add it via commandline from Ambari serve r: 

 

/var/lib/ambari-server/resources/scripts/configs.py -l <AMBARI_HOSTNAME> -t 8080 -u <USER_NAME> -p <PASSWORD> -a set -n <CLUSTER_NAME> -c yarn-env -k 'yarn.registry-dns.principal' -v 'yarn/_HOST@EXAMPLE.COM'

 

In the abouve example i am adding yarn/_HOST@EXAMPLE.COM as value of config : yarn.registry-dns.principal , see if this helps.

View in thread

2 replies

akhilsnaik
Gold ⭐️⭐️⭐️
akhilsnaikAnswer
Gold ⭐️⭐️⭐️
April 3, 2023

so it looks like Ambari is looking for an Configuration : yarn.registry-dns.principal and its missing in Configuration.

Can you see adding to yarn-env in Yarn Services configuration helps ? 

 

For ex , you can add it via commandline from Ambari serve r: 

 

/var/lib/ambari-server/resources/scripts/configs.py -l <AMBARI_HOSTNAME> -t 8080 -u <USER_NAME> -p <PASSWORD> -a set -n <CLUSTER_NAME> -c yarn-env -k 'yarn.registry-dns.principal' -v 'yarn/_HOST@EXAMPLE.COM'

 

In the abouve example i am adding yarn/_HOST@EXAMPLE.COM as value of config : yarn.registry-dns.principal , see if this helps.

Translate
    dch44
    dch44Author
    Silver ⭐️⭐️
    April 3, 2023

    It solved the problem

    Thanks

    Translate
    Terms & ConditionsAccessibility statement