@Bramantya Anggriawan I am going through the install doc, could you tell me the size of the cluster where you are installing the Metron? Do you have dedicated nodes for Metron? The above are just a quick view of some of the pre-requisites ... View more

@Vinay K I can see 2 things all connect to connectivity Received stat error from Zookeeper. code: CONNECTIONLOSS. Not retrying further znode monitoring connection errors. Can you validate your ZKFailoverControllers are running The root cause of a Socket Timeout is a connectivity failure between the machines. Check the settings: is this the machine you really wanted to talk to? - From the machine that is raising the exception, can you resolve the hostname. - Is that resolved hostname the correct one? Can you ping the remote host? - Is the target machine running the relevant Hadoop processes? - Can you telnet to the target host and port? - Can you telnet to the target host and port from any other machine? - On the target machine, can you telnet to the port using localhost as the hostname. If this works but external network connections time out, it's usually a firewall issue. Please check the above especially the firewall ... View more

@Bramantya Anggriawan Evidently the file /usr/hcp/1.4.1.0-18/metron/bin/zk_load_configs.sh seems to be missing ... View more

@Vinay K Can you confirm that the Active and Standby Namenodes were running normally and then suddenly the primary went down? Is there something, in particular, you did before the shutdown? Is the time on the QJM's servers in sync? Is this a test cluster? If so and you don't risk losing date then you could proceed with stopping the Hdfs service Start only the journal nodes (as they will need to be made aware of the formatting) On the first namenode (as user hdfs) $ hadoop namenode -format hdfs namenode -initializeSharedEdits -force For the journal nodes $ hdfs zkfc -formatZK -force To force zookeeper to reinitialise) restart that first namenode. On the second namenode $ hdfs namenode -bootstrapStandby -force (force synch with first namenode) On every datanode clear the data directory Restart the HDFS service This was a very simple step by step guide to formatting. ... View more

@Michael Bronson Wanted t have the same path like you ... View more

@Michael Bronson If its a production cluster then by precaution I advise you to contact hortonworks support hoping you subscribed. Secondly before upgrading the production you should have tested in DEV, UAT and maybe PREPROD and clearly documented all issues encountered and it's resolution, that's the safest and recommended path. You will have to resolve those issues before you can proceed, but as reiterated, before you finalize your upgrade your old version should still be usable as all the conf files still are pointing to HDP-2.6.0.3. To this $ cd /usr/hdp/current $ ll lrwxrwxrwx 1 root root 26 Mar 17 18:39 sqoop-client -> /usr/hdp/2.6.2.0-205/sqoop lrwxrwxrwx 1 root root 26 Mar 17 18:39 sqoop-server -> /usr/hdp/2.6.2.0-205/sqoop lrwxrwxrwx 1 root root 26 Mar 17 18:39 storm-client -> /usr/hdp/2.6.2.0-205/storm lrwxrwxrwx 1 root root 26 Mar 17 18:39 storm-nimbus -> /usr/hdp/2.6.2.0-205/storm lrwxrwxrwx 1 root root 40 Mar 17 18:39 storm-slider-client -> /usr/hdp/2.6.2.0-205/storm-slider-client This should still point to 2.6.0.3 I am still upgrading to an intermediary version ... View more

@Sandeep Ranjan I have just tried earlier and the download was triggered. Can you cancel and retry that is bizzare ... View more

@Sandeep Ranjan You only need to accept the terms 🙂 Do you have a pop-up blocker if so disable it? It should downlaod ... View more

@Michael Bronson My current version is HDP-2.6.2.0 so I am upgrading to HDP-2.6.3.0 then will do the 2.6.4.0-91 . Is that a production cluster? I think until you finalize(the moment symlinks are created to point to the new version) your previous version should still be usuable. !! ... View more