hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2553) BlockPoolSliceScanner spinning in loop
Date Sat, 17 Dec 2011 16:42:30 GMT

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

Uma Maheswara Rao G commented on HDFS-2553:
-------------------------------------------

{quote}
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hdfs.server.datanode.TestDataNodeMultipleRegistrations
{quote}
Test failure is unrelated to this patch. Filed separate JIRA for it HDFS-2700
                
> BlockPoolSliceScanner spinning in loop
> --------------------------------------
>
>                 Key: HDFS-2553
>                 URL: https://issues.apache.org/jira/browse/HDFS-2553
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Todd Lipcon
>            Assignee: Uma Maheswara Rao G
>            Priority: Critical
>         Attachments: CPUUsage.jpg, HDFS-2553.patch, HDFS-2553.patch
>
>
> Playing with trunk, I managed to get a DataNode in a situation where the BlockPoolSliceScanner
is spinning in the following loop, using 100% CPU:
>         at org.apache.hadoop.hdfs.server.datanode.DataNode$BPOfferService.isAlive(DataNode.java:820)
>         at org.apache.hadoop.hdfs.server.datanode.DataNode.isBPServiceAlive(DataNode.java:2962)
>         at org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner.scan(BlockPoolSliceScanner.java:625)
>         at org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner.scanBlockPoolSlice(BlockPoolSliceScanner.java:614)
>         at org.apache.hadoop.hdfs.server.datanode.DataBlockScanner.run(DataBlockScanner.java:95)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message