Member since
02-08-2016
793
Posts
669
Kudos Received
85
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1912 | 06-30-2017 05:30 PM | |
2461 | 06-30-2017 02:57 PM | |
1990 | 05-30-2017 07:00 AM | |
2394 | 01-20-2017 10:18 AM | |
4404 | 01-11-2017 02:11 PM |
09-13-2016
10:26 AM
You need to take care of Java if you are planing for Ambari and HDP upgrade.
... View more
09-13-2016
08:14 AM
what is the the current HDP version and the HDP version you are going to upgrade ? [If you are planing for hdp upgrade also]
... View more
09-07-2016
06:51 PM
Just modification in yum command - $yum clean all
... View more
09-07-2016
03:46 AM
@Donna Suddeth can you please accept best answer to close this thread. Thanks
... View more
08-31-2016
10:51 AM
@Savanna Endicott You can try below steps - 1. Login to ambari 2. Click on "admin" dropdown ->Manage Ambari -> click on "Views"-Add new view or you can check configuration for existing view. Pls find below screenshot -
... View more
08-29-2016
10:48 AM
3 Kudos
@Ashnee Sharma It seems there was issue while electing active namenode as per last checkpoint. To resolve this take both of the namenode down. [Note:Before this you want to make sure which namenode has latest metadata.] Start on of the namenode and make sure its performing fine. Then start the other namenode. Let me know if the resolves the issue.
... View more
08-29-2016
03:54 AM
@Sami Ahmad Did you tried to check the link given in error details - http://wiki.apache.org/hadoop/NoRouteToHost Pasting here : Some possible causes (not an exclusive list):
The hostname of the remote machine is wrong in the configuration files The client's host table /etc/hosts has an invalid IPAddress for the target host. The DNS server's host table has an invalid IPAddress for the target host. The client's routing tables (In Linux, iptables) are wrong. The DHCP server is publishing bad routing information. Client and server are on different subnets, and are not set up to talk to each other. This may be an accident, or it is to deliberately lock down the Hadoop cluster. The machines are trying to communicate using IPv6. Hadoop does not currently support IPv6 The host's IP address has changed but a long-lived JVM is caching the old value. This is a known problem with JVMs (search for "java negative DNS caching" for the details and solutions). The quick solution: restart the JVMs
... View more
08-26-2016
03:51 PM
@John Swartz Pls check if you are looking for this - http://hortonworks.com/blog/how-to-size-your-hadoop-cluster/
... View more
08-26-2016
03:50 PM
@John Swartz Pls check if you are looking for this - http://hortonworks.com/blog/how-to-size-your-hadoop-cluster/
... View more