@Manoj Dhake : Can you please share complete error log file? we get "Main class [org.apache.oozie.action.hadoop.HiveMain], exit code [40000]." in many senaerios ... View more

I have faced the same issue, used same steps to get standby namenode up and it worked. If you have any questions in following above steps please let me know. ... View more

Anandha L Ranganathan standby namenode and journal node configurations were in a corrupted state, so that when the cluster tried to switch to the standby, you encountered the error that you reported. Initially we have toW put the primary namenode into safemode and saved the namespace with the following commands: hdfs dfsadmin -safemode enter hdfs dfsadmin -saveNamespace su - hdfs -c "hdfs namenode -bootstrapStandby -force" this was to make sure that the namenode was in a consistent state before we attempted to restart the HDFS components one last time to make sure all processes started cleanly and that HDFS would automatically leave safemode ... View more

@sheetal: Are you sure? Because I have successfully captured bundle, but still I don't see an option of download, Even I have lost download option for previously captured bundles i.e. before the upgrade. You can see in the attached screenshot. ... View more

in FIFO, it will execute in the order you have submitted the job. Refer: http://hortonworks.com/blog/understanding-apache-hadoops-capacity-scheduler/ ... View more

Any update on this issue? ... View more

@Nasheb Ismaily: Yes, If job1 is using all the container then job2-job5 has to have wait, Else job2 will pick remaining container and start executing it. ... View more

This error is most probably caused due to the corrupt Image file that you’re are trying to import in Oracle Virtual Box. The error message also suggests that it’s failing due to check sum mismatch (VERR_TAR_CHKSUM_MISMATCH). or need to update my VirtualBox installation. ... View more

yes, perfect auth=KERBEROS;proxyuser=root ... View more