[
https://issues.apache.org/jira/browse/TEZ-4149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104701#comment-17104701
]
László Bodor edited comment on TEZ-4149 at 5/11/20, 5:42 PM:
-------------------------------------------------------------
okay, I refactored tez mini cluster and dfs cluster anyway into a wrapper class
for convenience
(I'm about to commit TEZ-4173 in order to fix current issues first, and then
sharing my patch here)
yeah, I think we should have your conf changes on tez mini cluster globally,
and having fair scheduler only in TestRecovery until further investigation
was (Author: abstractdog):
okay, I refactored tez mini cluster and dfs cluster anyway into a wrapper class
for convenience
I'm about to commit TEZ-4173 first, and then sharing my patch here
yeah, I think we should have your conf changes on tez mini cluster globally,
and having fair scheduler only in TestRecovery until further investigation
> Speed up TezRecovery tests
> --------------------------
>
> Key: TEZ-4149
> URL: https://issues.apache.org/jira/browse/TEZ-4149
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Jonathan Turner Eagles
> Assignee: László Bodor
> Priority: Major
> Attachments: TEZ-4149.WIP.patch,
> org.apache.tez.test.TestRecovery-output.txt
>
>
> Currently, approximately 50% of the tests cases are chosen to run as there
> are many failure points chosen to test recovery on.
> This can lead to the introduction of bugs into the code as not all test cases
> are run for every Tez QA run.
> In addition, this can be a real development bottleneck as tests take around
> 20 minutes per cycle if all tests are run (10 minutes if 50% of the tests are
> run as usual)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
