Member since
07-30-2019
453
Posts
112
Kudos Received
80
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2398 | 04-12-2023 08:58 PM | |
| 4970 | 04-04-2023 11:48 PM | |
| 1587 | 04-02-2023 10:24 PM | |
| 3470 | 07-05-2019 08:38 AM | |
| 3400 | 05-13-2019 06:21 AM |
08-09-2018
02:01 PM
Hi @Aviral Pathak , Are you logged in as Admin user ? also is the Blue tick there for your service. AFAIK This will happen either you are not an admin user instead you have just normal access or the Host is in heartbeat lost stage.
... View more
08-09-2018
01:34 PM
Hi @Paul Norris , As suggested can you please perform the command ambari-agent restart in your master node and See the logs if Agent registration is successful or not? I hope after restart of Agent node , It will be able to register, then you can restart your services as required. If it fails to register. please analyse the logs as mentioned in previous comment or attach the log snippet here. Hope this helps you.
... View more
08-09-2018
12:53 PM
Hi @Takefumi Oide , there is no way we can replace the white space in CN while you are syncing the LDAP to ambari. you might need to do it in LDAP only using ldapmodify command. Ambari just performs the sync based on the command like : ambari-server sync-ldap --ldap-sync-admin-name=admin --ldap-sync-admin-password=admin --all but in ranger, you can achieve the same. Follow this doc for the same : https://community.hortonworks.com/articles/86353/converting-spaces-in-usernames-or-group-names-in-r.html
... View more
08-09-2018
05:58 AM
Hi @Ilya Li, Oh this commands everything seems to be ok. Can you investigate further with this commands : 1) SELECT id, component_id, repo_version_id, state, user_name
FROM ambari.servicecomponent_version;
2) select * from servicecomponentdesiredstate where service_name='ZOOKEEPER';
3) select * from repo_version where repo_version_id in ( select desired_repo_version_id from servicecomponentdesiredstate where service_name='ZOOKEEPER');
4) select * from repo_version where repo_version_id in ( select desired_repo_version_id from servicecomponentdesiredstate);
5) select * from servicecomponentdesiredstate where desired_repo_version_id not in ( select repo_version_id from repo_version); If you happened to see two repo_versions in command 3 and 4 or get some output for command 5 ( which is empty in my env ) you can suspect that's the wrong entry in database and act accordingly. Hope this helps.
... View more
08-09-2018
03:54 AM
Hi @Ilya Li , Can you please have a look at this table select * from repo_version;
select * from stack; I hope you will get some clue. probably the stack_id of newly registered 3.1.2 will be pointing towards the wrong stack in stack table. As Amar suggested I would suggest you downgrade the cluster do the service checks on the zookeeper. change some configs in zookeeper and make sure it works. and then proceed with upgrade.
... View more
08-08-2018
05:34 PM
Hi @Paul Norris , This NPE is due to Ambari Agent failed to register with ambari-server(agent-register-processor-5) I would suggest you Abort the restart operation. See if there is any heartbeat lost b/w Ambari-agent and ambari-server. Restart Ambari-agent in the node. Make sure one service check on the a service on this node works fine. Then try to perform restart. without proper logs, I am afraid I cannot sense whats issue 😞 . It will be suggested you can raise a Case with Hortonworks Support Portal which will help you resolve this issue. Or you can even analyse /var/log/ambari-agent/ambari-agent.log<br>and <br>/var/log/ambari-server/ambari-server.log And update your findings here . i can try to help This is one similar BUG in Ambari-2.7.0 which I sense might be a root cause: https://issues.apache.org/jira/browse/AMBARI-23882 ,
... View more
08-08-2018
04:59 PM
Hi @Michael Bronson , can you set this parameter in Custom mapred site , and see if it works ? Reference : https://hadoop.apache.org/docs/stable/hadoop-mapreduce-client/hadoop-mapreduce-client-core/mapred-default.xml yarn.app.mapreduce.task.container.log.backups=3
yarn.app.mapreduce.am.container.log.limit.kb=102400
... View more
08-08-2018
04:32 PM
Hi @Ilya Li, Glad to hear your issue is resolved. If this comment helped you can you please accept this answer as Best answer so that other Users who face the issue will get Help from this.
... View more
08-08-2018
04:29 PM
Hi @Saurabh, If you add a custom yarn-site.xml property on Ambari like below yarn.nodemanager.webapp.https.address : <IP-ADDRESS>:8042 I see this can help you. you can try AFAIK it has to work. If it doesnt there is very little can be done from ambari point of view. Hope this helps.
... View more
08-08-2018
12:13 PM
Hi @Paul Norris , I just checked what should be the value of 'roleParams' once you are restarting the Appl Timeline server in my local cluster. [root@anaik1 data]# cat command-961.json |grep -i -5 roleParams
]
},
"clusterName": "asnaik",
"commandType": "EXECUTION_COMMAND",
"taskId": 961,
"roleParams": {
"component_category": "MASTER"
},
"componentVersionMap": {
"HDFS": {
"NAMENODE": "3.0.0.0-1634", It should be as above. Can you please verify what the value in your's using command cat /var/lib/ambari-agent/data/command-82.json |grep -i -5 roleParams If its empty. I would suggest you restart ambari server once and try again. If that doesnt worked. See in /var/log/ambari-server/ambari-server.log file while restarting the App timeline server. you will get some exceptions which will give clue whats going wrong. Hope this helps your in troubleshooting.
... View more