[
https://issues.apache.org/jira/browse/HDFS-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861559#action_12861559
]
dhruba borthakur commented on HDFS-1112:
----------------------------------------
The best bet is that the Nn should not allow any transactions while in
safemode. This means that any operation that needs to do transactions should
fail if the namenode is in safemode. Hairong is already proposing changing fsck
to not update access times via HDFS-1104.
I think we should also try to solve the general case where the NN does not
update access time of files if the NN is in safemode. Do you agree?
> Edit log buffer should not grow unboundedly
> -------------------------------------------
>
> Key: HDFS-1112
> URL: https://issues.apache.org/jira/browse/HDFS-1112
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.22.0
> Reporter: Hairong Kuang
> Fix For: 0.22.0
>
>
> Currently HDFS does not impose an upper limit on the edit log buffer. In case
> there are a large number of open operations coming in with access time update
> on, since open does not call sync automatically, there is a possibility that
> the buffer grow to a large size, therefore causes memory leak and full GC in
> extreme cases as described in HDFS-1104.
> The edit log buffer should be automatically flushed when the buffer becomes
> full.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
