[
https://issues.apache.org/jira/browse/HDFS-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747550#comment-13747550
]
Daryn Sharp commented on HDFS-5124:
-----------------------------------
Do we even need a read lock on the namespace at all? Token verification has
nothing to do with the namespace. On HADOOP-9880, I contemplated taking out
the locking in {{checkAvailableForRead}} because the pattern is used for
critical sections. However I decided to make the minimal change so I didn't
get called again on vacation. :)
As an aside, I'm currently trying to test a complete desync of the DTSM that
will parallelize token verification, acquisition, renewal, and cancellation
which will negate the read for this patch but it's probably a few days off.
> 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: Jing Zhao
> Priority: Blocker
> Attachments: 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
