[
https://issues.apache.org/jira/browse/HDFS-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726332#comment-14726332
]
Vinod Kumar Vavilapalli edited comment on HDFS-7830 at 9/1/15 10:41 PM:
------------------------------------------------------------------------
[~sjlee0] backported this to 2.6.1, after fixing minor merge issues. I just
pushed the commit to 2.6.1 after running compilation and
TestDataNodeHotSwapVolumes, TestFsDatasetImpl which changed in the patch.
was (Author: vinodkv):
[~sjlee0] backported this to 2.6.1, after fixing minor issues (with java
diamond operator). I just pushed the commit to 2.6.1 after running compilation
and TestFsDatasetImpl which changed in the patch.
> 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
> Labels: 2.6.1-candidate
> Fix For: 2.7.0, 2.6.1
>
> Attachments: HDFS-7830.000.patch, HDFS-7830.001.patch,
> HDFS-7830.002.patch, HDFS-7830.003.patch, HDFS-7830.004.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)
