hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ming Ma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1897) CLI and core support for signal container functionality
Date Thu, 24 Sep 2015 16:47:04 GMT

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

Ming Ma commented on YARN-1897:

Thanks [~xgong].

Regarding the diagnosis, do you want to allow the end user to specify the reason from CLI/YarnClient?
If it is generated only by YARN components, we can also use enum similar to {{CMgrCompletedContainersEvent}}'s

That also brings up the issue where RM and NM continue to use {{NodeHeartbeatResponse}}'s
{{ContainersToCleanup}} to kill containers due to preemption. Should we migrate it to {{ContainersToSignalList}}?
But that could be a separate jira.

The patch already prints all signals supported if you don't specify any parameter. Do you
want an explicit option called "-all"?

yarn container
usage: container
 -help                                     Displays help for all commands.
 -list <Application Attempt ID>            List containers for application
 -signal <container ID [signal command]>   Signal the container. The
                                           available signal commands are
                                           FORCEFUL_SHUTDOWN] Default
                                           command is OUTPUT_THREAD_DUMP.
 -status <Container ID>                    Prints the status of the

> CLI and core support for signal container functionality
> -------------------------------------------------------
>                 Key: YARN-1897
>                 URL: https://issues.apache.org/jira/browse/YARN-1897
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>         Attachments: YARN-1897-2.patch, YARN-1897-3.patch, YARN-1897-4.patch, YARN-1897-5.patch,
YARN-1897-6.patch, YARN-1897-7.patch, YARN-1897.1.patch
> We need to define SignalContainerRequest and SignalContainerResponse first as they are
needed by other sub tasks. SignalContainerRequest should use OS-independent commands and provide
a way to application to specify "reason" for diagnosis. SignalContainerResponse might be empty.

This message was sent by Atlassian JIRA

View raw message