You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Sunil Govindan (JIRA)" <ji...@apache.org> on 2018/11/23 12:01:02 UTC
[jira] [Updated] (MAPREDUCE-7119) Avoid stopContainer on failed
node
[ https://issues.apache.org/jira/browse/MAPREDUCE-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunil Govindan updated MAPREDUCE-7119:
--------------------------------------
Target Version/s: 3.3.0 (was: 3.2.0)
Bulk update: moved all 3.2.0 non-blocker issues, please move back if it is a blocker.
> Avoid stopContainer on failed node
> ----------------------------------
>
> Key: MAPREDUCE-7119
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7119
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
> Affects Versions: 2.8.4
> Reporter: Brandon Scheller
> Priority: Minor
> Labels: bug, bugfix, stopContainer
>
> Avoid stopContainer on failed node
>
> If a container failed to launch earlier due to terminated instances, it has already been removed from the container hash map. Avoiding the kill() for CONTAINER_REMOTE_CLEANUP will avoid wasting 15min per container on retries/timeout.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org