You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ARAVINDA REDDY N (JIRA)" <ji...@apache.org> on 2019/03/17 14:25:00 UTC

[jira] [Updated] (IGNITE-11508) Yarn Ignite deployment: Add support to over ride queue name through cluster properties

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

ARAVINDA REDDY N updated IGNITE-11508:
--------------------------------------
    Attachment: IGNITE_11508_Implemented_yarn_queue_override_feature_for_Yarn_Deployment.patch

> Yarn Ignite deployment: Add support to over ride queue name through cluster properties
> --------------------------------------------------------------------------------------
>
>                 Key: IGNITE-11508
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11508
>             Project: Ignite
>          Issue Type: Improvement
>          Components: yarn
>    Affects Versions: 2.7
>            Reporter: ARAVINDA REDDY N
>            Assignee: ARAVINDA REDDY N
>            Priority: Minor
>         Attachments: IGNITE_11508_Implemented_yarn_queue_override_feature_for_Yarn_Deployment.patch
>
>
> Yarn ignite 2.7.0 doesn't have the facility to provide queue name through the cluster.properties. When i checked the IgniteYarnClient source code by default it is set to "default".
> // Finally, set-up ApplicationSubmissionContext for the application
>  ApplicationSubmissionContext appContext = app.getApplicationSubmissionContext();
>  appContext.setApplicationName("ignition"); // application name
>  appContext.setAMContainerSpec(amContainer);
>  appContext.setResource(capability);
>  appContext.setQueue("default"); // queue
>  
> It would be a great support if we can allow overriding it through cluster properties.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)