Hi @forest lin , Can you please pause the upgrade, Make the configuration change and Try to resume the upgrade? As per current ambari design once upgrade is going on all configuration changes will be at paused stage. Thanks, Akhil ... View more

Hi @Shobhna Dhami , thanks for attaching the trace. From Trace, it seems like you have a mytest.example.com that already exists in database. I would suggest you raise a case with hortonworks support if you are a customer so that our engineers can fix this issue for you. Or else. Follow this steps . 1) take a DB backup ( so that you can restore incase you got something wrong in database) pg_dump -U ambari ambari > ./ambari_$(date +"%Y%m%d%H%M%S").sql 2) stop Ambari-server 3) login to Postgres ( default password will be bigdata) [root@aanaik1 ~]# psql -U ambari ambari Password for user ambari: psql (9.2.23) Type "help" for help. ambari=> select host_id,host_name,ipv4,public_host_name from ambari.hosts; ambari=> SELECT * FROM ambari.hoststate; <br> you might find some duplicate entries for the host_name mytest.example.com. you need to remove existing hosts after verifying that they do not have any services installed and not in use. you can run the command : ambari=> select * from hoststate where host_id in (select host_id from hosts where host_name like '%mytest.example.com%'); ambari=> delete from hoststate where host_id in (select host_id from hosts where host_name like '%mytest.example.com%'); ambari=> select * from hosts where host_name like '%mytest.example.com%' ; ambari=> delete from hosts where host_name like '%mytest.example.com%' ; and then try to run the host update command again. This commands are as per my understanding on the issue. you might need to investigate based on contents of ambari.hosts and ambari.hoststate table as you are more aware then me about your cluster configuration. I would suggest if it's your production cluster then you can actually contact hortonworks support for this operation here: https://hortonworks.com/services/support/ hope this helps. If this helps. Please accept the answer so that it will be helpfull for other users facing same issue. . ... View more

Hi @Guozhen Li , This error seems to be generic and doesn't give any clue. Can you go into /var/lib/ambai-agent/data/errors-2610.txt and also output-2610.txt and see if you can find any clue, attach its output.. Additionally, you can do inspect /var/log/ambari-server/ambari-server.log and see what error its thrown and attach here. Hope you have added this in core-site of hdfs hadoop.proxyuser.root.groups=* hadoop.proxyuser.root.hosts=* ... View more

Hi @Michael Bronson , I see you want to perform this operation via REST API , I see the rest api method is very tough at you need to fetch the whole configs first, add your own configs and use PUT method to save it. I would suggest you use config.py method. for ex: below commands worked for me. Please note i use admin/admin and my cluster name is asnaik , [root@anaik1 ~]# /var/lib/ambari-server/resources/scripts/configs.py --user=admin --password=admin --port=8080 --action=set --host=anaik1 --cluster=asnaik --config-type=yarn-site --key=yarn.nodemanager.localizer.cache.target-size-mb --value=10240 [root@anaik1 ~]# /var/lib/ambari-server/resources/scripts/configs.py --user=admin --password=admin --port=8080 --action=set --host=anaik1 --cluster=asnaik --config-type=yarn-site --key=yarn.nodemanager.localizer.cache.cleanup.interval-ms --value=300000 Please mark the thread as resolved if this answers your query. Let me know if you need the harder method. can help you with that too. but requires two REST API calls and some shell scripting. ... View more