You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Erik Krogen (JIRA)" <ji...@apache.org> on 2019/03/08 23:06:00 UTC
[jira] [Created] (HDFS-14349) Edit log may be rolled more
frequently than necessary with multiple Standby nodes
Erik Krogen created HDFS-14349:
----------------------------------
Summary: 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
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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org