[ https://issues.apache.org/jira/browse/HDFS-14349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795105#comment-16795105 ]
Erik Krogen commented on HDFS-14349: ------------------------------------ Hi [~starphin], thanks for the input. I agree that the _auto-roll_ operation is performed by the ANN. However, SbNNs trigger the original/"normal" edit log roll via {{NamenodeProtocol#rollEditLog()}}. This is triggered by the {{EditLogTailer}} on the SbNN which has a {{rollEditsRpcExecutor}}. > Edit log may be rolled more frequently than necessary with multiple Standby > nodes > --------------------------------------------------------------------------------- > > Key: HDFS-14349 > URL: https://issues.apache.org/jira/browse/HDFS-14349 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, hdfs, qjm > Reporter: Erik Krogen > Assignee: Ekanth Sethuramalingam > Priority: Major > > When HDFS-14317 was fixed, we tackled the problem that in a cluster with > in-progress edit log tailing enabled, a Standby NameNode may _never_ roll the > edit logs, which can eventually cause data loss. > Unfortunately, in the process, it was made so that if there are multiple > Standby NameNodes, they will all roll the edit logs at their specified > frequency, so the edit log will be rolled X times more frequently than they > should be (where X is the number of Standby NNs). This is not as bad as the > original bug since rolling frequently does not affect correctness or data > availability, but may degrade performance by creating more edit log segments > than necessary. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org