You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2010/06/18 01:15:24 UTC
[jira] Created: (HDFS-1243) 0.20 append: Replication tests in
TestFileAppend4 should not expect immediate replication
0.20 append: Replication tests in TestFileAppend4 should not expect immediate replication
-----------------------------------------------------------------------------------------
Key: HDFS-1243
URL: https://issues.apache.org/jira/browse/HDFS-1243
Project: Hadoop HDFS
Issue Type: Test
Components: test
Affects Versions: 0.20-append
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Minor
Fix For: 0.20-append
Attachments: hdfs-1243.txt
The replicationTest() cases in TestFileAppend4 currently assume that the file has both valid replicas immediately after completing the file. However, the datanodes may take some milliseconds to report the replica - we should only expect 1 replica (fs.replication.min) immediately after close, and we should allow up to a second or so before asserting that we reach replication 2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HDFS-1243) 0.20 append: Replication tests in
TestFileAppend4 should not expect immediate replication
Posted by "Nicolas Spiegelberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892401#action_12892401 ]
Nicolas Spiegelberg commented on HDFS-1243:
-------------------------------------------
+1 was seeing the same problem in our daily builds and independently made a similar fix
> 0.20 append: Replication tests in TestFileAppend4 should not expect immediate replication
> -----------------------------------------------------------------------------------------
>
> Key: HDFS-1243
> URL: https://issues.apache.org/jira/browse/HDFS-1243
> Project: Hadoop HDFS
> Issue Type: Test
> Components: test
> Affects Versions: 0.20-append
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Fix For: 0.20-append
>
> Attachments: hdfs-1243.txt
>
>
> The replicationTest() cases in TestFileAppend4 currently assume that the file has both valid replicas immediately after completing the file. However, the datanodes may take some milliseconds to report the replica - we should only expect 1 replica (fs.replication.min) immediately after close, and we should allow up to a second or so before asserting that we reach replication 2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HDFS-1243) 0.20 append: Replication tests in
TestFileAppend4 should not expect immediate replication
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HDFS-1243:
------------------------------
Attachment: hdfs-1243.txt
This patch got rid of the occasional spurious failures on my hudson.
> 0.20 append: Replication tests in TestFileAppend4 should not expect immediate replication
> -----------------------------------------------------------------------------------------
>
> Key: HDFS-1243
> URL: https://issues.apache.org/jira/browse/HDFS-1243
> Project: Hadoop HDFS
> Issue Type: Test
> Components: test
> Affects Versions: 0.20-append
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Fix For: 0.20-append
>
> Attachments: hdfs-1243.txt
>
>
> The replicationTest() cases in TestFileAppend4 currently assume that the file has both valid replicas immediately after completing the file. However, the datanodes may take some milliseconds to report the replica - we should only expect 1 replica (fs.replication.min) immediately after close, and we should allow up to a second or so before asserting that we reach replication 2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.