[
https://issues.apache.org/jira/browse/HDFS-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272814#comment-14272814
]
Hadoop QA commented on HDFS-7533:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12691530/HDFS-7533.v1.txt
against trunk revision ef3c3a8.
{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.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/9181//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9181//console
This message is automatically generated.
> Datanode sometimes does not shutdown on receiving upgrade shutdown command
> --------------------------------------------------------------------------
>
> Key: HDFS-7533
> URL: https://issues.apache.org/jira/browse/HDFS-7533
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Kihwal Lee
> Assignee: Eric Payne
> Attachments: HDFS-7533.v1.txt
>
>
> When datanode is told to shutdown via the dfsadmin command during rolling
> upgrade, it may not shutdown. This is because not all writers have responder
> running, but sendOOB() tries anyway. This causes NPE and the shutdown thread
> dies, halting the shutdown after only shutting down DataXceiverServer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)