[
https://issues.apache.org/jira/browse/TEZ-4149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104651#comment-17104651
]
Jonathan Turner Eagles commented on TEZ-4149:
---------------------------------------------
While testing with Fair Scheduler should be viable, I'm surprised it makes a
difference like this. There must be some Capacity Scheduler configuration that
delays scheduling to improve placement. I'm ok making this change as it is a
quick way to large improvements. I would want the changes made globally in
MiniTezCluster as likely that will give improvements in other testes as well.
> 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)
