Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 29 Jun 2017 22:48:00 +0000 (UTC)
From: "Chen Liang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13082634.1498510189000.139637.1498776480362@Atlassian.JIRA>
In-Reply-To: <JIRA.13082634.1498510189000@Atlassian.JIRA>
References: <JIRA.13082634.1498510189000@Atlassian.JIRA> <JIRA.13082634.1498510189844@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HDFS-12043) Add counters for block re-replication
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 29 Jun 2017 22:48:08 -0000


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

Chen Liang updated HDFS-12043:
------------------------------
    Attachment: HDFS-12043.004.patch

Thanks [~arpitagarwal] who pointed out offline that the use of thread.sleep() in the test can be reliable. Post v004 patch to use {{GenericTestUtils.waitFor()}} instead.

> Add counters for block re-replication
> -------------------------------------
>
>                 Key: HDFS-12043
>                 URL: https://issues.apache.org/jira/browse/HDFS-12043
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Chen Liang
>            Assignee: Chen Liang
>         Attachments: HDFS-12043.001.patch, HDFS-12043.002.patch, HDFS-12043.003.patch, HDFS-12043.004.patch
>
>
> We occasionally see that the under-replicated block count is not going down quickly enough. We've made at least one fix to speed up block replications (HDFS-9205) but we need better insight into the current state and activity of the block re-replication logic. For example, we need to understand whether is it because re-replication is not making forward progress at all, or is it because new under-replicated blocks are being added faster.
> We should include additional metrics:
> # Cumulative number of blocks that were successfully replicated. 
> # Cumulative number of re-replications that timed out.
> # Cumulative number of blocks that were dequeued for re-replication but not scheduled e.g. because they were invalid, or under-construction or replication was postponed.
>  
> The growth rate of of the above metrics will make it clear whether block replication is making forward progress and if not then provide potential clues about why it is stalled.
> Thanks [~arpitagarwal] for the offline discussions.


--
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