You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2014/12/09 00:07:12 UTC

[jira] [Commented] (SAMZA-491) Support a non-default queue in YARN

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

Chris Riccomini commented on SAMZA-491:
---------------------------------------

This looks good. [~metacret], did you try this on a cluster?

> Support a non-default queue in YARN
> -----------------------------------
>
>                 Key: SAMZA-491
>                 URL: https://issues.apache.org/jira/browse/SAMZA-491
>             Project: Samza
>          Issue Type: Bug
>          Components: yarn
>    Affects Versions: 0.9.0
>            Reporter: Chris Riccomini
>             Fix For: 0.9.0
>
>         Attachments: SAMZA-491.patch
>
>
> Samza always submits its jobs to YARN's default queue. We should make this configurable.
> I believe that the steps are:
> 1) Add a `yarn.queue` field to YarnConfig.
> 2) Update YarnJob.scala's submit() method to get the yarn queue, and use it in the client.submitApplication() call.
> 3) Update ClientHelper.scala's submitApplication() method to take an optional queue, and if it's set, add it to the ApplicationSubmissionContext, as I described above.



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