[ 
https://issues.apache.org/jira/browse/TEZ-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558441#comment-16558441
 ] 

TezQA commented on TEZ-3952:
----------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12933217/TEZ-3952.005.patch
  against master revision dd6a09d.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2882//console

This message is automatically generated.


> Allow Tez task speculation to grant greater customization of certain 
> parameters
> -------------------------------------------------------------------------------
>
>                 Key: TEZ-3952
>                 URL: https://issues.apache.org/jira/browse/TEZ-3952
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Nishant Dash
>            Assignee: Nishant Dash
>            Priority: Major
>         Attachments: TEZ-3952.001.patch, TEZ-3952.002.patch, 
> TEZ-3952.003.patch, TEZ-3952.004.patch, TEZ-3952.005.patch
>
>
> Many of the settings for Tez task speculation are hardcoded and should 
> instead be configurable. For example, there's no equivalent config settings 
> for the following MapReduce settings:
> - mapreduce.job.speculative.speculative-cap-running-tasks
> - mapreduce.job.speculative.retry-after-no-speculate
> - mapreduce.job.speculative.retry-after-speculate
> - mapreduce.job.speculative.minimum-allowed-tasks
> - mapreduce.job.speculative.speculative-cap-total-tasks



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to