You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "shanyu zhao (JIRA)" <ji...@apache.org> on 2016/02/20 00:55:18 UTC

[jira] [Updated] (SLIDER-1089) Slider client should print out applicationId before submit Yarn application

     [ https://issues.apache.org/jira/browse/SLIDER-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

shanyu zhao updated SLIDER-1089:
--------------------------------
    Attachment: SLIDER-1089.patch

Patch attached. I also changed scope from private to protected for startCluster() and checkForCredentials() so that someone can override actionCreate() in a subclass.

Since mostly the change is rearrange code and print out some information. There is no need to add additional unit tests.

> Slider client should print out applicationId before submit Yarn application
> ---------------------------------------------------------------------------
>
>                 Key: SLIDER-1089
>                 URL: https://issues.apache.org/jira/browse/SLIDER-1089
>             Project: Slider
>          Issue Type: Bug
>          Components: client
>    Affects Versions: Slider 0.81, Slider 0.90.2
>            Reporter: shanyu zhao
>         Attachments: SLIDER-1089.patch
>
>
> Today for creating a cluster, the Slider client first submit the Yarn application, then print out the applicationId. When submission process crashed, there's no way for the client to know whether or not the application is actually submitted. We should print out the applicationId before running the submission code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)