[
https://issues.apache.org/jira/browse/HDFS-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505946#comment-13505946
]
Suresh Srinivas commented on HDFS-4233:
---------------------------------------
Given rollEditLog is called by secondary, which in turn calls startEditLog, the
failure to roll an editlog results in failure of an RPC call from secondary to
primary. The issue reported here is very likely to happen in setups that use
secondary namenode, even in branch-2.
bq. Of course, in order to be immune to FD exhaustion, NN should not close the
file until a new one is opened.
FD exhaustion is an interesting bug. I agree we should probably open a file and
then finalize the previous segment. I also think we will have to add limit on
number of connections accepted by the RPC server.
> NN keeps serving even after no journals started while rolling edit
> ------------------------------------------------------------------
>
> Key: HDFS-4233
> URL: https://issues.apache.org/jira/browse/HDFS-4233
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.5
> Reporter: Kihwal Lee
> Priority: Critical
>
> We've seen namenode keeps serving even after rollEditLog() failure. Instead
> of taking a corrective action or regard this condition as FATAL, it keeps on
> serving and modifying its file system state. No logs are written from this
> point, so if the namenode is restarted, there will be data loss.
--
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
