[
https://issues.apache.org/jira/browse/TEZ-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873333#comment-15873333
]
Siddharth Seth commented on TEZ-3627:
-------------------------------------
bq. The setQueueName happens in YarnTaskSchedulerService.start, doesn't this
get invoked during DAGAppMaster serviceInit, no dag should start before this is
complete right?
Happens in a different thread though, and I believe the dispatcher thread, RPC
threads have already been created by this point. Wouldn't visibility come into
play in this case?
> Use queue name available in RegisterApplicationMasterResponse.
> --------------------------------------------------------------
>
> Key: TEZ-3627
> URL: https://issues.apache.org/jira/browse/TEZ-3627
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Harish Jaiprakash
> Assignee: Harish Jaiprakash
> Attachments: TEZ-3627.01.patch, TEZ-3627.02.patch
>
>
> The queue name was already being sent in RegisterApplicationMasterResponse
> from yarn. Use that instead of the environment variable to set the queue name.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
