Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 6 May 2015 03:34:36 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12559486.1338957035000.15346.1430883276537@Atlassian.JIRA>
In-Reply-To: <JIRA.12559486.1338957035000@Atlassian.JIRA>
References: <JIRA.12559486.1338957035000@Atlassian.JIRA>
 <JIRA.12559486.1338957035929@arcas>
Subject: [jira] [Updated] (HDFS-3512) Delay in scanning blocks at DN side
 when there are huge number of blocks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Allen Wittenauer updated HDFS-3512:
-----------------------------------
    Labels: BB2015-05-TBR  (was: )

> Delay in scanning blocks at DN side when there are huge number of blocks
> ------------------------------------------------------------------------
>
>                 Key: HDFS-3512
>                 URL: https://issues.apache.org/jira/browse/HDFS-3512
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>    Affects Versions: 2.0.0-alpha
>            Reporter: suja s
>            Assignee: amith
>              Labels: BB2015-05-TBR
>         Attachments: HDFS-3512.patch
>
>
> Block scanner maintains the full list of blocks at DN side in a map and there is no differentiation between the blocks which are already scanned and the ones not scanend. For every check (ie every 5 secs) it will pick one block and scan. There are chances that it chooses a block which is already scanned which leads to further delay in scanning of blcoks which are yet to be scanned.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)