[
https://issues.apache.org/jira/browse/HDFS-8914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14963812#comment-14963812
]
Allen Wittenauer commented on HDFS-8914:
----------------------------------------
The process is relatively simple:
a) contributor submits a patch
b) QA bot does static analysis to cover some of the review work
c) committer reads through patch after QA bot says it is good
d) committer gives a +1 if it is good, -1 or general feedback if it has issues
e) if good, committer commits against source tree for releases that the
committer feels it should be in, etc
f) patch shows up in next release that contains that patch
So even if this were to get committed right this second, it likely won't show
up on the website for a very long time. Also keep in mind that there are
literally hundreds of JIRAs in patch available state. It can take a while for
someone to get to it.
> Documentation conflict regarding fail-over of Namenode
> ------------------------------------------------------
>
> Key: HDFS-8914
> URL: https://issues.apache.org/jira/browse/HDFS-8914
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: documentation
> Affects Versions: 2.7.1
> Environment: Documentation page in live
> Reporter: Ravindra Babu
> Assignee: Lars Francke
> Priority: Trivial
> Attachments: HDFS-8914.1.patch
>
>
> Please refer to these two links and correct one of them.
> http://hadoop.apache.org/docs/r2.7.1/hadoop-project-dist/hadoop-hdfs/HdfsDesign.html
> The NameNode machine is a single point of failure for an HDFS cluster. If the
> NameNode machine fails, manual intervention is necessary. Currently,
> automatic restart and failover of the NameNode software to another machine is
> not supported.
> http://hadoop.apache.org/docs/r2.7.1/hadoop-project-dist/hadoop-hdfs/HDFSHighAvailabilityWithQJM.html
> The HDFS High Availability feature addresses the above problems by providing
> the option of running two redundant NameNodes in the same cluster in an
> Active/Passive configuration with a hot standby. This allows a fast failover
> to a new NameNode in the case that a machine crashes, or a graceful
> administrator-initiated failover for the purpose of planned maintenance.
> Please update hdfsDesign article with same facts to avoid confusion in
> Reader's mind..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
