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 namen
Thanks @vinayakumarb for the reply,
Seems we are using QJM (3 journal nodes) from 2.6 apache hadoop branch.
dfs.namenode.shared.edits.dir
qjournal://:;:;:/
On Thu, Aug 20, 2015 at 8:05 PM, Vinayakumar B
wrote:
> Actually SSH fencing was
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 in advance :).
We are using apache hadoop 2.6 branch.
On Thu, Aug 20, 2015 at 7:33 PM, Raju Bairishetti wrote:
> Hello devs,
>
> We are hitting an issue, in which none of the namenodes are in active
> state.
>
> Our Setup:
> ---
>We are using *automatic failover* for Had
Hello devs,
We are hitting an issue, in which none of the namenodes are in active
state.
Our Setup:
---
We are using *automatic failover* for Hadoop Namenode HA(two node) and
*SshFencing* as fencing mechanism
*1) What happens if namenode host goes down?*
* This is caus
