[jira] [Commented] (HDFS-5384) Add a new TransitionState to indicate NN is in transition from standby state to active state
[ https://issues.apache.org/jira/browse/HDFS-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14524726#comment-14524726 ] Hadoop QA commented on HDFS-5384: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:red}-1{color} | patch | 0m 0s | The patch command could not apply the patch during dryrun. | \\ \\ || Subsystem || Report/Notes || | Patch URL | http://issues.apache.org/jira/secure/attachment/12609503/HDFS-5384.001.patch | | Optional Tests | javadoc javac unit findbugs checkstyle | | git revision | trunk / f1a152c | | Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/10576/console | This message was automatically generated. Add a new TransitionState to indicate NN is in transition from standby state to active state Key: HDFS-5384 URL: https://issues.apache.org/jira/browse/HDFS-5384 Project: Hadoop HDFS Issue Type: Improvement Components: ha, namenode Affects Versions: 3.0.0 Reporter: Jing Zhao Assignee: Jing Zhao Attachments: HDFS-5384.000.patch, HDFS-5384.001.patch Currently in HA setup, when a NameNode is transitioning from standby to active, the current code first sets the state of the NN to Active, then starts the active service, during which the NN still needs to tail the remaining editlog and may not be able to serve certain requests as expected (such as HDFS-5322). So it may be necessary to define a transition state to indicate that NN has left the previous state and is in transitioning to the next state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-5384) Add a new TransitionState to indicate NN is in transition from standby state to active state
[ https://issues.apache.org/jira/browse/HDFS-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13801108#comment-13801108 ] Hadoop QA commented on HDFS-5384: - {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12609503/HDFS-5384.001.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}. The javadoc tool did not generate any 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 1.3.9) 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-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/5249//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5249//console This message is automatically generated. Add a new TransitionState to indicate NN is in transition from standby state to active state Key: HDFS-5384 URL: https://issues.apache.org/jira/browse/HDFS-5384 Project: Hadoop HDFS Issue Type: Improvement Components: ha, namenode Affects Versions: 3.0.0 Reporter: Jing Zhao Assignee: Jing Zhao Attachments: HDFS-5384.000.patch, HDFS-5384.001.patch Currently in HA setup, when a NameNode is transitioning from standby to active, the current code first sets the state of the NN to Active, then starts the active service, during which the NN still needs to tail the remaining editlog and may not be able to serve certain requests as expected (such as HDFS-5322). So it may be necessary to define a transition state to indicate that NN has left the previous state and is in transitioning to the next state. -- This message was sent by Atlassian JIRA (v6.1#6144)