[
https://issues.apache.org/jira/browse/HDFS-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178596#comment-13178596
]
Aaron T. Myers commented on HDFS-2737:
--------------------------------------
I also support option 3 from above. I see little advantage to option 2, as it's
only slightly simpler than 3 and we might as well reuse the EditLogTailer
thread. Option 1 (rolling based on time or # txns) is really only a
(potentially poor) proxy for #3, and doesn't seem much simpler.
> 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
