hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tarun Parimi (Jira)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-7278) Speculative execution behavior is observed even when mapreduce.map.speculative and mapreduce.reduce.speculative are false
Date Tue, 19 May 2020 09:48:00 GMT

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

Tarun Parimi commented on MAPREDUCE-7278:
-----------------------------------------

The mvn install error seems to be completely unrelated to this patch. [~wilfreds], [~prabhujoseph]
Can you please have a look when you get time?
{code:java}
[INFO] --- exec-maven-plugin:1.3.1:exec (check-jar-contents) @ hadoop-client-check-invariants
---
[ERROR] Found artifact with unexpected contents: '/home/jenkins/jenkins-slave/workspace/PreCommit-MAPREDUCE-Build/sourcedir/hadoop-client-modules/hadoop-client-runtime/target/hadoop-client-runtime-3.4.0-SNAPSHOT.jar'
    Please check the following and either correct the build or update
    the allowed list with reasoning.

    microsoft/
    microsoft/sql/
    microsoft/sql/DateTimeOffset$1.class
    microsoft/sql/DateTimeOffset$SerializationProxy.class
    microsoft/sql/DateTimeOffset.class
    microsoft/sql/Types.class
{code}


> Speculative execution behavior is observed even when mapreduce.map.speculative and mapreduce.reduce.speculative
are false
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-7278
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7278
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: task
>    Affects Versions: 2.8.0, 3.4.0
>            Reporter: Tarun Parimi
>            Assignee: Tarun Parimi
>            Priority: Major
>         Attachments: MAPREDUCE-7278.001.patch, MAPREDUCE-7278.002.patch, MAPREDUCE-7278.003.patch,
Screen Shot 2020-04-30 at 8.04.27 PM.png
>
>
> When a failed task attempt container is stuck in FAIL_FINISHING_CONTAINER state for some
time, we observe two task attempts are launched simultaneously even when speculative execution
is disabled.
> This results in the below message shown in the killed attempts, indicating speculation
has occurred. This is an issue for jobs which require speculative execution to be strictly
disabled.
>   !Screen Shot 2020-04-30 at 8.04.27 PM.png!
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org


Mime
View raw message