[ 
https://issues.apache.org/jira/browse/IGNITE-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796002#comment-16796002
 ] 

Ilya Kasnacheev commented on IGNITE-11508:
------------------------------------------

[~ARAVINDAREDDY] Please take a look at Pull Request (in Links section), tell me 
if I have missed something while migrating your 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: Ilya Kasnacheev
>            Priority: Minor
>             Fix For: 2.8
>
>         Attachments: 
> IGNITE_11508_Implemented_yarn_queue_override_feature_for_Yarn_Deployment.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)

Reply via email to