Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <29303519.1175841332538.JavaMail.jira@brutus>
Date: Thu, 5 Apr 2007 23:35:32 -0700 (PDT)
From: "Tom White (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-1149) DFS Scalability: high cpu usage in
 addStoredBlock
In-Reply-To: <20257411.1174596752175.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tom White updated HADOOP-1149:
------------------------------

    Status: Open  (was: Patch Available)

Raghu, I think this one needs regenerating too due to FSNamesystem conflicts.

> DFS Scalability: high cpu usage in addStoredBlock
> -------------------------------------------------
>
>                 Key: HADOOP-1149
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1149
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>            Reporter: dhruba borthakur
>         Assigned To: Raghu Angadi
>             Fix For: 0.13.0
>
>         Attachments: HADOOP-1149.patch
>
>
> I have seen addStoredBlock() consume lots of CPU. One possible cause is that it invokes proccessOverReplicatedBlock. The logic to find and purge over-replicated blocks can be done much less often.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.