[
https://issues.apache.org/jira/browse/HDFS-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748072#comment-13748072
]
Daryn Sharp commented on HDFS-5124:
-----------------------------------
The more I look at this, HADOOP-9880 did not cause this issue. The deadlocks
are a pre-existing bug resulting from HDFS-3083 adding
{{checkAvailableForRead}}.
I've fully tested the small patch I've posted since we've seen a number of
variants of this deadlock. The larger locking changes I alluded to are
intended for a different jira.
> Namenode in secure cluster deadlocks
> ------------------------------------
>
> Key: HDFS-5124
> URL: https://issues.apache.org/jira/browse/HDFS-5124
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.1.1-beta
> Environment: Secure Hadoop 2 cluster
> Reporter: Deepesh Khandelwal
> Assignee: Daryn Sharp
> Priority: Blocker
> Attachments: HADOOP-5124.patch, HDFS-5124.001.patch,
> HDFS-5124.002.patch, nn_jstack.out
>
>
> Namenode deadlocks after a while in use.
--
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
