[jira] [Resolved] (HDFS-2737) HA: Automatically trigger log rolls periodically on the active NN

["Aaron T. Myers (Resolved) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDFS-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aaron T. Myers resolved HDFS-2737.
----------------------------------

       Resolution: Fixed
    Fix Version/s: HA branch (HDFS-1623)
     Hadoop Flags: Reviewed

Thanks a lot for the reviews, Todd. I've just committed this to the HA branch.
                
> 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: Aaron T. Myers
>             Fix For: HA branch (HDFS-1623)
>
>         Attachments: HDFS-2737-HDFS-1623.patch, HDFS-2737-HDFS-1623.patch, HDFS-2737-HDFS-1623.patch, HDFS-2737-HDFS-1623.patch, hdfs-2737-prelim.txt
>
>
> 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