hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhankun Tang (Jira)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-14349) Edit log may be rolled more frequently than necessary with multiple Standby nodes
Date Mon, 26 Aug 2019 14:16:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-14349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915819#comment-16915819

Zhankun Tang commented on HDFS-14349:

Bulk update: Preparing for 3.1.3 release. moved all 3.1.3 non-blocker issues to 3.1.4, please
move back if it is a blocker for you.

> 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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message