[
https://issues.apache.org/jira/browse/HDFS-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183093#comment-13183093
]
Suresh Srinivas commented on HDFS-2737:
---------------------------------------
For the time being, it is okay not to read the editlog in progress and trigger
editlog rolling using existing JournalProtocol mechanism. We should revisit
this in the future to read editlog in progress.
> HA: Automatically trigger log rolls periodically on the active NN
> -----------------------------------------------------------------
>
> Key: HDFS-2737
> URL: https://issues.apache.org/jira/browse/HDFS-2737
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
>
> Currently, the edit log tailing process can only read finalized log segments.
> So, if the active NN is not rolling its logs periodically, the SBN will lag a
> lot. This also causes many datanode messages to be queued up in the
> PendingDatanodeMessage structure.
> To combat this, the active NN needs to roll its logs periodically -- perhaps
> based on a time threshold, or perhaps based on a number of transactions. I'm
> not sure yet whether it's better to have the NN roll on its own or to have
> the SBN ask the active NN to roll its logs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
