[
https://issues.apache.org/jira/browse/HDFS-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747765#comment-13747765
]
Chris Nauroth commented on HDFS-5124:
-------------------------------------
bq. Once those 5 jam up waiting on the FSN lock, the listener thread is going
to keep accepting sockets as fast as he can - at least until an OOM
This is the first time I noticed this logic. Thanks for pointing it out.
Shouldn't a properly tuned listen backlog prevent OOM though? Or have you seen
one of those cases where the OS doesn't really enforce the listen backlog you
requested?
At this point, I'm really torn on whether or not to hold the namesystem lock.
(Damned if we do, damned if we don't.) Risk of OOM could tip the scale though.
> 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
