hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luca Telloli (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-456) Problems with dfs.name.edits.dirs as URI
Date Fri, 17 Jul 2009 10:31:14 GMT

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

Luca Telloli commented on HDFS-456:
-----------------------------------

Today I've got different results from yours, I'm not sure if it's related to my environment
configuration. 

I tried these 3 configurations: 
1 - trunk 
2 - trunk with HDFS-456 applied
3 - trunk with HDFS-396 reverted. 396 doesn't revert fully anymore but the problem is related
to CreateEditLog.java, so not relevant to this issue 

My outcome is: 
1 - TestReplication fails with messages such as, which I guess is expected: 
{noformat}
Testcase: testPendingReplicationRetry took 0.469 sec
        Caused an ERROR
All specified directories are not accessible or do not exist.
java.io.IOException: All specified directories are not accessible or do not exist.
{noformat}

2 - TestReplication failed on testReplicateLenMismatchedBlock with error: 
{noformat}
Testcase: testReplicateLenMismatchedBlock took 2.375 sec
        Caused an ERROR
The requested operation cannot be performed on a file with a user-mapped section open
java.io.IOException: The requested operation cannot be performed on a file with a user-mapped
section open
        at java.io.RandomAccessFile.setLength(Native Method)
        at org.apache.hadoop.hdfs.TestDatanodeBlockScanner.changeReplicaLength(TestDatanodeBlockScanner.java:419)
        at org.apache.hadoop.hdfs.TestReplication.changeBlockLen(TestReplication.java:424)
        at org.apache.hadoop.hdfs.TestReplication.testReplicateLenMismatchedBlock(TestReplication.java:403)
{noformat}

3 - TestReplication passed correctly 
{noformat}
luca@yahoo-a170c7579 /tmp/patches/trunk-applied
$ tail -n 6 build/test/TEST-org.apache.hadoop.hdfs.TestReplication.txt

Testcase: testBadBlockReportOnTransfer took 24.61 sec
Testcase: testReplicationSimulatedStorag took 3.562 sec
Testcase: testReplication took 9.359 sec
Testcase: testPendingReplicationRetry took 23.797 sec
Testcase: testReplicateLenMismatchedBlock took 10.953 sec
{noformat}

so at the end everything seems fine. I'm still puzzled on why the test didn't fail today and
failed yesterday

> Problems with dfs.name.edits.dirs as URI
> ----------------------------------------
>
>                 Key: HDFS-456
>                 URL: https://issues.apache.org/jira/browse/HDFS-456
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.21.0
>            Reporter: Konstantin Shvachko
>            Assignee: Luca Telloli
>             Fix For: 0.21.0
>
>         Attachments: failing-tests.zip, HDFS-456.patch, HDFS-456.patch, HDFS-456.patch,
HDFS-456.patch
>
>
> There are several problems with recent commit of HDFS-396.
> # It does not work with default configuration "file:///". Throws {{IllegalArgumentException}}.
> # *ALL* hdfs tests fail on Windows because "C:\mypath" is treated as an illegal URI.
Backward compatibility is not provided.
> # {{IllegalArgumentException}} should not be thrown within hdfs code because it is a
{{RuntimException}}. We should throw {{IOException}} instead. This was recently discussed
in another jira.
> # Why do we commit patches without running unit tests and test-patch? This is the minimum
requirement for a patch to qualify as committable, right?

-- 
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