hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4120) Add a new "-skipSharedEditsCheck" option for BootstrapStandby
Date Fri, 18 Jul 2014 11:15:06 GMT

    [ https://issues.apache.org/jira/browse/HDFS-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066277#comment-14066277
] 

Hadoop QA commented on HDFS-4120:
---------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12656471/HDFS-4120.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs
hadoop-hdfs-project/hadoop-hdfs/src/contrib/bkjournal.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/7382//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7382//console

This message is automatically generated.

> 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: Rakesh R
>            Priority: Minor
>             Fix For: 2.6.0
>
>         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)

Mime
View raw message