Member since
03-14-2016
4721
Posts
1111
Kudos Received
874
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2509 | 04-27-2020 03:48 AM | |
| 4976 | 04-26-2020 06:18 PM | |
| 4056 | 04-26-2020 06:05 PM | |
| 3289 | 04-13-2020 08:53 PM | |
| 5015 | 03-31-2020 02:10 AM |
05-16-2018
02:25 PM
This might help to other people. This seems like a bug : https://issues.apache.org/jira/browse/AMBARI-21687 The bug is fixed in 2.6.0.0 branch only ( not fixed in 2.4.x.x or 2.5.x.x versions of ambari). So, The available workaround is to add the node via 'Admin' user or use the ambari 2.6.x
... View more
10-25-2017
09:58 AM
Jay not in this issue , but I will happy to get tour answer about my quastion from - https://community.hortonworks.com/questions/142356/how-to-recover-the-standby-name-node-in-ambari-clu.html
... View more
10-25-2017
07:33 AM
@ANSARI FAHEEM AHMED Can you please let us know how you created that user & HDFS Directory (The exact command that you used) Or you used some other tool / Java code to do that? Or if you used any AD/LDAP to sync the users?
... View more
07-19-2018
02:41 PM
I copied /usr/hdp/current/atlas-client/hook/storm/atlas-storm-plugin-impl/storm-bridge-xxx.xxxxxxxxx.jar to /usr/hdp/current/storm-client/lib
/usr/hdp/current/storm-client/lib/usr/hdp/current/storm-client/extlib but it didin't work.
... View more
01-22-2019
07:31 PM
@deepak rathod I have encountered the same issue. Did you able to fix it? If yes, can you please share the solution here. Thanks in advance.
... View more
10-25-2017
07:58 AM
Thanks a lot @Jay SenSharma for your help. Today when i was login to my AWS machine. it does not start all service and give me an error 8080:Port and Ambari Server issue. I just Go inot @nameNode and write command : Service Iptables Stop and both issue solves 🙂 🙂 Hope it will work smoothly. Thanks again
... View more
10-18-2017
03:18 AM
@Jay SenSharma Thanks for helping out. Restarting the shellinabox service in the sandbox helped me to access the webssh.
... View more
12-08-2017
04:53 AM
Thanks @Jonathan Hurley got your point regarding raising question. My @Namenode was on Safemode that time when i was facing this alert. i put the @namenode into Normal mode. now the alert Purge. is this exactly the reason ? whats your views Thanks
... View more
10-13-2018
11:26 AM
This was fixed for me by updating fqdn name to point to domain name by updating /etc/hosts and resolv.conf.
... View more
10-11-2017
12:38 PM
@Aditya Sirna That's it. Thank you so much.
... View more