[
https://issues.apache.org/jira/browse/FLINK-13548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900099#comment-16900099
]
thy commented on FLINK-13548:
-----------------------------
[~walterddr]: Thanks for your advice!
First, I would say sorry that I made a mistake between our internal spark and
community spark. The internal spark is implemented as what I talked above.
Actually the community spark does not implement the yarn application priority.
1. As mentioned in YARN official doc about "Cluster-level priority": Any
application submitted with a priority greater than the cluster-max priority
will have its priority reset to the cluster-max priority. I think maybe it is
not necessary to limit 1-9, just make sure that the priority is not negative.
2. The queue’s default priority will be used for any application submitted
without a specified priority. An idea to envision the default value is that we
set the default YARN PRIORITY OPTION to -1. Once we get -1 from the option, we
do not set "appcontext.setPriority". Maybe there is a better choice?
Thanks
thy
> Support priority of the Flink YARN application
> ----------------------------------------------
>
> Key: FLINK-13548
> URL: https://issues.apache.org/jira/browse/FLINK-13548
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Reporter: thy
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, Flink 1.9 does not support yarn priority submission. The default
> priority of yarn submission jobs is 1.
> Based on this, we can provide a ConfigOption in YarnConfigOptions. The
> submission of the priority range from 1 to 9(from low to high priority). When
> the user does not configure the parameters, the priority is still 1.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
