[
https://issues.apache.org/jira/browse/YARN-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994865#comment-13994865
]
Vinod Kumar Vavilapalli commented on YARN-1515:
-----------------------------------------------
bq. Vinod Kumar Vavilapalli, I am interested in your feedback in the context of
your comment on MAPREDUCE-5044 .
Yeah, sorry. This was in my blind spot. I understand this patch was online for
a while, and is likely also being run in production, but I have some comments.
As I mentioned on MAPREDUCE-5044, this feature is and should be done via
YARN-445. Dumping threads is strictly a java construct and so far we have
avoided any language feature in the YARN APIs (not willingly anyways). Can we
instead implement this feature using YARN-445 and getting clients/AMs to send a
SIGQUIT signal or some such signal command instead? I looked at the patch and
that is indeed what it is doing eventually in the NM. We need to keep the API
clean. Thoughts?
> Ability to dump the container threads and stop the containers in a single RPC
> -----------------------------------------------------------------------------
>
> Key: YARN-1515
> URL: https://issues.apache.org/jira/browse/YARN-1515
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: api, nodemanager
> Reporter: Gera Shegalov
> Assignee: Gera Shegalov
> Attachments: YARN-1515.v01.patch, YARN-1515.v02.patch,
> YARN-1515.v03.patch, YARN-1515.v04.patch, YARN-1515.v05.patch,
> YARN-1515.v06.patch, YARN-1515.v07.patch
>
>
> This is needed to implement MAPREDUCE-5044 to enable thread diagnostics for
> timed-out task attempts.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
