[
https://issues.apache.org/jira/browse/HDFS-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759987#comment-13759987
]
Hudson commented on HDFS-5164:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #4376 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/4376/])
HDFS-5164. DeleteSnapshot should check if OperationCategory.WRITE is possible
before taking write lock (contributed by Colin Patrick McCabe) (cmccabe:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1520492)
* /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/namenode/FSNamesystem.java
> deleteSnapshot should check if OperationCategory.WRITE is possible before
> taking write lock
> -------------------------------------------------------------------------------------------
>
> Key: HDFS-5164
> URL: https://issues.apache.org/jira/browse/HDFS-5164
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.3.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Priority: Minor
> Fix For: 2.3.0
>
> Attachments: HDFS-5164.001.patch
>
>
> deleteSnapshot should check if OperationCategory.WRITE is possible before
> taking the write lock, to help avoid lock contention
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
