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

Hudson commented on HDFS-6569:
------------------------------

FAILURE: Integrated in Hadoop-Hdfs-trunk #1842 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1842/])
HDFS-6569. OOB message can't be sent to the client when DataNode shuts down for 
upgrade. Contributed by Brandon Li (brandonli: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1618742)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BlockReceiver.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNode.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataXceiver.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataXceiverServer.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestDataNodeRollingUpgrade.java


> OOB message can't be sent to the client when DataNode shuts down for upgrade
> ----------------------------------------------------------------------------
>
>                 Key: HDFS-6569
>                 URL: https://issues.apache.org/jira/browse/HDFS-6569
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>    Affects Versions: 3.0.0, 2.4.0
>            Reporter: Brandon Li
>            Assignee: Brandon Li
>             Fix For: 2.6.0
>
>         Attachments: HDFS-6569.001.patch, HDFS-6569.002.patch, 
> HDFS-6569.003.patch, test-hdfs-6569.patch
>
>
> The socket is closed too early before the OOB message can be sent to client, 
> which causes the write pipeline failure.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to