[
https://issues.apache.org/jira/browse/HDFS-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066170#comment-14066170
]
Hudson commented on HDFS-4120:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #5910 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5910/])
reverted
HDFS-4120. Add a new "-skipSharedEditsCheck" option for BootstrapStandby (
Contributed by Rakesh R )
........ (vinayakumarb:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1611560)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/bkjournal/src/test/java/org/apache/hadoop/contrib/bkjournal/TestBootstrapStandbyWithBKJM.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/BootstrapStandby.java
HDFS-4120. Add a new "-skipSharedEditsCheck" option for BootstrapStandby (
Contributed by Rakesh R ) (vinayakumarb:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1611556)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/bkjournal/src/test/java/org/apache/hadoop/contrib/bkjournal/TestBootstrapStandbyWithBKJM.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/BootstrapStandby.java
> Add a new "-skipSharedEditsCheck" option for BootstrapStandby
> -------------------------------------------------------------
>
> Key: HDFS-4120
> URL: https://issues.apache.org/jira/browse/HDFS-4120
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: ha, namenode
> Affects Versions: 3.0.0, 2.0.2-alpha
> Reporter: Liang Xie
> Assignee: Liang Xie
> Priority: Minor
> Attachments: HDFS-4120.patch, HDFS-4120.patch, HDFS-4120.patch,
> HDFS-4120.txt
>
>
> Per
> https://issues.apache.org/jira/browse/HDFS-3752?focusedCommentId=13449466&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13449466
> , let's introduce a new option, it should be very safe, but really useful
> for some corner case. e.g. when SNN losts local storage, we need to reset
> SNN, but in current trunk, it'll always get a FATAL msg and could never be
> successful. Another workaroud for this case, is full-sync the "current"
> directory from ANN, but it'll be cost more disk-space & net bandwidth, IMHO.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
