Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 5 Apr 2013 19:57:16 +0000 (UTC)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12640209.1364866472619.118631.1365191836762@arcas>
In-Reply-To: <JIRA.12640209.1364866472619@arcas>
References: <JIRA.12640209.1364866472619@arcas>
Subject: [jira] [Commented] (HDFS-4657) If incremental BR is received before
 first full BR NN will log a line for every block on a DN
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Todd Lipcon commented on HDFS-4657:
-----------------------------------

I agree something like #3 makes sense. Let's just put a limit on the number of blocks logged in any BR (something like 1000 or even 10000).
                
> If incremental BR is received before first full BR NN will log a line for every block on a DN
> ---------------------------------------------------------------------------------------------
>
>                 Key: HDFS-4657
>                 URL: https://issues.apache.org/jira/browse/HDFS-4657
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.0.4-alpha
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>
> This can impact restart times pretty substantially if the DNs have a lot of blocks, and since the FSNS write lock is held while processing the block report clients will not make any progress.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira