You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hairong Kuang (JIRA)" <ji...@apache.org> on 2009/03/05 23:33:56 UTC
[jira] Updated: (HADOOP-5412) TestInjectionForSimulatedStorage
oaccasionally fails on timeout
[ https://issues.apache.org/jira/browse/HADOOP-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hairong Kuang updated HADOOP-5412:
----------------------------------
Attachment: simulatedLoop.patch
The patch does the following:
1. Disallow a simulated datanode to write to a block if the block is being written;
2. In the test, make sure that all datanodes are up before injecting blocks. This could greatly reduce the chance that NN schedules two concurrent replications to the same datanode.
> TestInjectionForSimulatedStorage oaccasionally fails on timeout
> ---------------------------------------------------------------
>
> Key: HADOOP-5412
> URL: https://issues.apache.org/jira/browse/HADOOP-5412
> Project: Hadoop Core
> Issue Type: Bug
> Affects Versions: 0.18.3
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.18.4
>
> Attachments: simulatedLoop.patch
>
>
> Occasionally TestInjectionForSimulatedStorage falls into an infinite loop, waiting for a block to reach its replication factor. The log repeatedly prints the following message:
> dfs.TestInjectionForSimulatedStorage (TestInjectionForSimulatedStorage.java:waitForBlockReplication(89)) - Not enough replicas for 2th block blk_6302924909504458109_1001 yet. Expecting 4, got 2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.