[
https://issues.apache.org/jira/browse/HDFS-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354124#comment-14354124
]
Hadoop QA commented on HDFS-7830:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12703521/HDFS-7830.002.patch
against trunk revision d6e05c5.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:red}-1 javac{color}. The applied patch generated 1156 javac
compiler warnings (more than the trunk's current 1155 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/9804//testReport/
Javac warnings:
https://builds.apache.org/job/PreCommit-HDFS-Build/9804//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9804//console
This message is automatically generated.
> DataNode does not release the volume lock when adding a volume fails.
> ---------------------------------------------------------------------
>
> Key: HDFS-7830
> URL: https://issues.apache.org/jira/browse/HDFS-7830
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
> Affects Versions: 2.6.0
> Reporter: Lei (Eddy) Xu
> Assignee: Lei (Eddy) Xu
> Attachments: HDFS-7830.000.patch, HDFS-7830.001.patch,
> HDFS-7830.002.patch
>
>
> When there is a failure in adding volume process, the {{in_use.lock}} is not
> released. Also, doing another {{-reconfig}} to remove the new dir in order to
> cleanup doesn't remove the lock. lsof still shows datanode holding on to the
> lock file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
