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-7714) Simultaneous restart of HA NameNodes and DataNode can cause DataNode to register successfully with only one NameNode.
Date Mon, 02 Feb 2015 22:39:35 GMT

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

Hadoop QA commented on HDFS-7714:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12695806/HDFS-7714-001.patch
  against trunk revision 3472e3b.

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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:red}-1 release audit{color}.  The applied patch generated 1 release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs:

                  org.apache.hadoop.hdfs.server.datanode.TestDataNodeMultipleRegistrations
                  org.apache.hadoop.hdfs.TestDFSRollback
                  org.apache.hadoop.hdfs.TestDFSUpgrade
                  org.apache.hadoop.hdfs.server.datanode.TestBPOfferService
                  org.apache.hadoop.hdfs.TestRollingUpgrade
                  org.apache.hadoop.net.TestNetworkTopology
                  org.apache.hadoop.hdfs.TestDFSStartupVersions

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/9394//testReport/
Release audit warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/9394//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9394//console

This message is automatically generated.

> Simultaneous restart of HA NameNodes and DataNode can cause DataNode to register successfully
with only one NameNode.
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-7714
>                 URL: https://issues.apache.org/jira/browse/HDFS-7714
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>    Affects Versions: 2.6.0
>            Reporter: Chris Nauroth
>            Assignee: Vinayakumar B
>         Attachments: HDFS-7714-001.patch
>
>
> In an HA deployment, DataNodes must register with both NameNodes and send periodic heartbeats
and block reports to both.  However, if NameNodes and DataNodes are restarted simultaneously,
then this can trigger a race condition in registration.  The end result is that the {{BPServiceActor}}
for one NameNode terminates, but the {{BPServiceActor}} for the other NameNode remains alive.
 The DataNode process is then in a "half-alive" state where it only heartbeats and sends block
reports to one of the NameNodes.  This could cause a loss of storage capacity after an HA
failover.  The DataNode process would have to be restarted to resolve this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message