[
https://issues.apache.org/jira/browse/HDFS-14349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhankun Tang updated HDFS-14349:
--------------------------------
Target Version/s: 3.0.4, 3.3.0, 3.2.1, 3.1.4 (was: 3.0.4, 3.3.0, 3.2.1,
3.1.3)
> 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
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
