Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 31 Jul 2017 18:37:00 +0000 (UTC)
From: "Arpit Agarwal (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13084489.1499163022000.54330.1501526220299@Atlassian.JIRA>
In-Reply-To: <JIRA.13084489.1499163022000@Atlassian.JIRA>
References: <JIRA.13084489.1499163022000@Atlassian.JIRA> <JIRA.13084489.1499163022688@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HDFS-12082) BlockInvalidateLimit value is
 incorrectly set after namenode heartbeat interval reconfigured
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 31 Jul 2017 18:37:04 -0000


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

Arpit Agarwal updated HDFS-12082:
---------------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 3.0.0-beta1
                   2.9.0
           Status: Resolved  (was: Patch Available)

I've committed this. Thanks for the contribution [~cheersyang] and thanks for the code review [~vagarychen].

> BlockInvalidateLimit value is incorrectly set after namenode heartbeat interval reconfigured 
> ---------------------------------------------------------------------------------------------
>
>                 Key: HDFS-12082
>                 URL: https://issues.apache.org/jira/browse/HDFS-12082
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs, namenode
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>             Fix For: 2.9.0, 3.0.0-beta1
>
>         Attachments: HDFS-12082.001.patch, HDFS-12082.002.patch, HDFS-12082.003.patch, HDFS-12082.004.patch
>
>
> HDFS-1477 provides an option to reconfigured namenode heartbeat interval without restarting the namenode. When the heartbeat interval is reconfigured, {{blockInvalidateLimit}} gets recounted
> {code}
>  this.blockInvalidateLimit = Math.max(20 * (int) (intervalSeconds),
>         DFSConfigKeys.DFS_BLOCK_INVALIDATE_LIMIT_DEFAULT);
> {code}
> this doesn't honor the existing value set by {{dfs.block.invalidate.limit}}.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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