[
https://issues.apache.org/jira/browse/HDFS-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747804#comment-13747804
]
Kihwal Lee commented on HDFS-5124:
----------------------------------
bq. I think you may have more problems blocking the clients on the FSN lock
during standby transition instead of throwing an exception immediately.
For one, if all reader threads are blocked on FSN lock, no more RPC calls will
get through, even HA admin commands such as HA state transition. For example,
if SBN was checkpointing holding the write lock and sufficient number of
token-based rpc connections are made during this, HA admin command will get
blocked until checkpointing is done. Such command is supposed to interrupt
on-going checkpointing and initiate transition right away.
> 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
