[
https://issues.apache.org/jira/browse/HDFS-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748086#comment-13748086
]
Daryn Sharp commented on HDFS-5124:
-----------------------------------
The big issue with leaving the FSN locking in place: 5 token connections will
block all connections, including kerberos connections, from being processed.
The socket readers will not process any incoming connections. Admin commands
will not be able to run.
I should note the concern over token auth clients not blocking during a standy
to active transition is not an issue. Kerberos clients currently enter the FSN
and immediately receive a {{StandbyException}} so token clients should
conceptually behave no differently. If the failover proxy cannot handle this
condition, it needs to be fixed.
> 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
