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 "GAO Rui (JIRA)" <ji...@apache.org> on 2015/12/11 08:47:11 UTC
[jira] [Commented] (HDFS-9403) Erasure coding: some EC tests are
missing timeout
[ https://issues.apache.org/jira/browse/HDFS-9403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052363#comment-15052363 ]
GAO Rui commented on HDFS-9403:
-------------------------------
Hi [~zhz]], according to existing unit test timeout setting, I suggest to set all the timeout of EC related test cases to 60000. Then, run the cases, if there are some cases running into timeout, we could adjust the timeout for these cases according to the test scenarios. Does this make sense?
> Erasure coding: some EC tests are missing timeout
> -------------------------------------------------
>
> Key: HDFS-9403
> URL: https://issues.apache.org/jira/browse/HDFS-9403
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: erasure-coding, test
> Affects Versions: 3.0.0
> Reporter: Zhe Zhang
> Assignee: GAO Rui
> Priority: Minor
>
> EC data writing pipeline is still being worked on, and bugs could introduce program hang. We should add a timeout for all tests involving striped writing. I see at least the following:
> * {{TestErasureCodingPolicies}}
> * {{TestFileStatusWithECPolicy}}
> * {{TestDFSStripedOutputStream}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)