hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Payne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5044) Have AM trigger jstack on task attempts that timeout before killing them
Date Thu, 19 May 2016 19:21:13 GMT

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

Eric Payne commented on MAPREDUCE-5044:

[~mingma], thank you for your reply and explanation.
- signalContainers was initially suggested as an ordered list of signalContainer. So it could
include requests from the same container or requests from different containers. It is true
that the only use case we know of so far is to include requests from the same container.
In that case, do we want to call it something like {{signalsToContainers}}? I'm open for ideas.

- Will the required in the protocol buffer definition create any issue if we do rolling upgrade
from 2.8 to 2.9 and the 2.9 MR AM might send a list of SignalContainerCommandProto to 2.8
NM? Maybe 2.8 NM just discards the message, not a big deal. Regardless, that is a separate
issue that we don't need to address it here.
Yes, this is a concern and something we need to look into more deeply and keep in mind.

> Have AM trigger jstack on task attempts that timeout before killing them
> ------------------------------------------------------------------------
>                 Key: MAPREDUCE-5044
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5044
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mr-am
>    Affects Versions: 2.1.0-beta
>            Reporter: Jason Lowe
>            Assignee: Gera Shegalov
>         Attachments: MAPREDUCE-5044.008.patch, MAPREDUCE-5044.009.patch, MAPREDUCE-5044.v01.patch,
MAPREDUCE-5044.v02.patch, MAPREDUCE-5044.v03.patch, MAPREDUCE-5044.v04.patch, MAPREDUCE-5044.v05.patch,
MAPREDUCE-5044.v06.patch, MAPREDUCE-5044.v07.local.patch, Screen Shot 2013-11-12 at 1.05.32
PM.png, Screen Shot 2013-11-12 at 1.06.04 PM.png
> When an AM expires a task attempt it would be nice if it triggered a jstack output via
SIGQUIT before killing the task attempt.  This would be invaluable for helping users debug
their hung tasks, especially if they do not have shell access to the nodes.

This message was sent by Atlassian JIRA

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

View raw message