hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2256) TestBlockReplacement unit test failed.
Date Thu, 29 Nov 2007 01:29:43 GMT

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

Hairong Kuang updated HADOOP-2256:
----------------------------------

    Attachment: blockReplacement2.patch

This patch removes the change to the rpc server.

> TestBlockReplacement unit test failed.
> --------------------------------------
>
>                 Key: HADOOP-2256
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2256
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.16.0
>            Reporter: Raghu Angadi
>            Assignee: Hairong Kuang
>             Fix For: 0.16.0
>
>         Attachments: blockReplacement.patch, blockReplacement1.patch, blockReplacement2.patch,
TestBlockReplacement-log.txt, TestBlockReplacement-log.txt
>
>
> I will attach the log. Part of the log :
> {noformat}
> junit] 2007-11-20 18:44:13,559 WARN  dfs.DataNode (DataNode.java:copyBlock(1128)) - Got
exception 
> while serving blk_-8824434176426942280 to 127.0.0.1:50011: java.io.IOException: 
> Block blk_-8824434176426942280 is not valid.
>     [junit] 	at org.apache.hadoop.dfs.FSDataset.getBlockFile(FSDataset.java:549)
>     [junit] 	at org.apache.hadoop.dfs.FSDataset.getMetaFile(FSDataset.java:466)
>     [junit] 	at org.apache.hadoop.dfs.FSDataset.getMetaDataInputStream(FSDataset.java:480)
>     [junit] 	at org.apache.hadoop.dfs.DataNode$BlockSender.<init>(DataNode.java:1282)
>     [junit] 	at org.apache.hadoop.dfs.DataNode$DataXceiver.copyBlock(DataNode.java:1098)
>     [junit] 	at org.apache.hadoop.dfs.DataNode$DataXceiver.run(DataNode.java:861)
>     [junit] 	at java.lang.Thread.run(Thread.java:595)
> {noformat}
> Summery might look like same as HADOOP-2200 but symptoms in log are different and I think
the reason is different.

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


Mime
View raw message