I found the terminology of primary and secondary to be a bit confusing in
describing operation after a failure scenario. Perhaps it is helpful to
think that the Hadoop instance is guided to select a node as primary for
normal operation. If that node fails, then the backup becomes the new
primary.
Prior to the Hadoop 2.x series, the NameNode was a single point of failure in
anHDFS cluster — in other words, if the machine on which the single NameNodewas
configured became unavailable, the entire cluster would be unavailableuntil the
NameNode could be restarted. This was bad news,
I have a kerberized cluster of hadoop,which works fine for a long time. It is a
CDH version of 5.1.2
Lately, i want to add oozie as another component of my cluster.
Everything goes fine until this step:
hadoop@gdc-dn06-69:~/oozie$ ./bin/oozie-setup.sh sharelib create -fs
Hi Mark,
Thanks for giving detailed information about name node failure and High
availability feature.
Wish you all the best in your job search.
Thanks again...
Regards,
Chandrash3khar Kotekar
Mobile - +91 8600011455
On Mon, Dec 15, 2014 at 6:29 AM, mark charts mcha...@yahoo.com wrote:
