[
https://issues.apache.org/jira/browse/YARN-8898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661487#comment-16661487
]
Botong Huang commented on YARN-8898:
------------------------------------
Hi [~bibinchundatt], good questions.
bq. Application priority update, what should be the behaviour if subcluster's
priorities are not same. Should we be considering appriority of home cluster
always?
Since I missed this priority field when I port the code to trunk, right now
UAMs in secondary sub-clusters didn't set this priority at all in their
ApplicationSubmissionContext in UnmanagedApplicationMaster. By browsing the
code, my understanding is once submitted, the app priority won't change any
more, correct? I think we should submit the UAMs with the right priority in the
first place.
bq. Also in case of async response from subcluster we should maintain response
order too.
bq. If response from home cluster not received during merge of response,
probably we have to remember the last response from home cluster.
For these two, I am actually already doing this in YARN-8933. Please take a
look. I think we should just always take the priority in the last remembered
home response.
> Fix FederationInterceptor#allocate to set application priority in
> allocateResponse
> ----------------------------------------------------------------------------------
>
> Key: YARN-8898
> URL: https://issues.apache.org/jira/browse/YARN-8898
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Bibin A Chundatt
> Assignee: Bilwa S T
> Priority: Major
>
> In case of FederationInterceptor#mergeAllocateResponses skips
> application_priority in response returned
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
