[
https://issues.apache.org/jira/browse/HDFS-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753935#comment-13753935
]
Suresh Srinivas edited comment on HDFS-5140 at 8/29/13 6:59 PM:
----------------------------------------------------------------
I think if SBN crosses the threshold and is in the process of moving out of
safemode, it does not make sense to enter safemode again. +1 for not going back
to safemode as the block count keeps changing. Other alternative solutions seem
needlessly complicated at no obvious benefits.
was (Author: sureshms):
I think if SBN cross the threshold and is in the process of moving out of
safemode, it does not make sense to enter safemode again. +1 for not going back
to safemode as the block count keeps changing. Other alternative solutions seem
needlessly complicated at no obvious benefits.
> Too many safemode monitor threads being created in the standby namenode
> causing it to fail with out of memory error
> -------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-5140
> URL: https://issues.apache.org/jira/browse/HDFS-5140
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha
> Affects Versions: 2.1.0-beta
> Reporter: Arpit Gupta
> Assignee: Jing Zhao
> Priority: Blocker
>
> While running namenode load generator with 100 threads for 10 mins namenode
> was being failed over ever 2 mins.
> The standby namenode shut itself down as it ran out of memory and was not
> able to create another thread.
> When we searched for 'Safe mode extension entered' in the standby log it was
> present 55000+ times
--
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