Seems fencing mechanism is still required with apache hadoop 2.6 branch to avoid split brain case. We are already using 3 journal code node quorum in production. We are not able to bring it standby to active in case of active namenode host down.
What should be the better way to bring stnadby namenode to active when the active namenode host down (with hadoop 2.6) ? On Fri, Aug 21, 2015 at 8:16 AM, Raju Bairishetti <raju....@gmail.com> wrote: > Thanks @vinayakumarb for the reply, > > Seems we are using QJM (3 journal nodes) from 2.6 apache hadoop branch. > > <property> > > <name>dfs.namenode.shared.edits.dir</name> > > <value> > qjournal://<journalnode1>:<port>;<journalnode2>:<port>;<journalnode3>:<port>/<journalId> > </value> > > </property> > > On Thu, Aug 20, 2015 at 8:05 PM, Vinayakumar B <vinayakum...@apache.org> > wrote: > >> Actually SSH fencing was introduced before QuorumJournal was there to >> ensure only one active writer at all times. >> >> If you are using QuorumJournal for shared edits.. you dont need to >> configure SSH fencing. QuorumJournal will ensure its allowing only one >> writer at a time. >> >> -Vinay >> > > > > -- > Thanks > Raju Bairishetti, > > www.inmobi.com > > > > > *2012 ME Best Mobile Ad Network Award Winner > > [image: http://www.inmobi.com/press-releases/files/2013/02/MIT.png] > > >
