hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yoram Arnon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-159) name node at 100% cpu, making redundant replications
Date Mon, 01 May 2006 20:39:47 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-159?page=comments#action_12377280 ] 

Yoram Arnon commented on HADOOP-159:
------------------------------------

It was observed just twice, in the same timeframe.

I'm not aware of any patches that attempt to address this. Logging was added though.
Let's wait a while before closing, unless there's a specific fix.

> name node at 100% cpu, making redundant replications
> ----------------------------------------------------
>
>          Key: HADOOP-159
>          URL: http://issues.apache.org/jira/browse/HADOOP-159
>      Project: Hadoop
>         Type: Bug

>   Components: dfs
>     Versions: 0.1.1
>     Reporter: Yoram Arnon
>     Assignee: Sameer Paranjpye
>     Priority: Blocker
>      Fix For: 0.2

>
> some hours after adding some new nodes to the cluster, the name node went into a state
where it's consuming 100% cpu.
> The log file keeps logging messages of the forms
> 060421 155049 Obsoleting block blk_8093115169359854355
> 060421 155049 Pending transfer (block blk_-6965677235456960523) from node1383:50010 to
2 destinations
> 060421 155049 Block report from node1283:50010: 2140 blocks.
> 060421 155049 Redundant addStoredBlock request received for block blk_-6836937139917042917
on node node1143:50010
> many DFS operations time out, making useful work impossible.
> restarting dfs solved the problem for a while, but it came back within an hour.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message