[
https://issues.apache.org/jira/browse/MAPREDUCE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582431#comment-17582431
]
ASF GitHub Bot commented on MAPREDUCE-7407:
-------------------------------------------
ashutoshcipher opened a new pull request, #4779:
URL: https://github.com/apache/hadoop/pull/4779
### Description of PR
Avoid stopContainer() on dead node
### For code changes:
- [X] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> Avoid stopContainer() on dead node
> ----------------------------------
>
> Key: MAPREDUCE-7407
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7407
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 3.3.4
> Reporter: groot
> Assignee: groot
> Priority: Major
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
