[
https://issues.apache.org/jira/browse/FLINK-13548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16899652#comment-16899652
]
Rong Rong commented on FLINK-13548:
-----------------------------------
Hi [~boswell], thanks for bringing up this discussion. I think this is indeed a
good feature to have. Several questions regarding the idea here:
1. do we need to limit the priority to 1-9? According to [YARN official
doc|https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html#Setup_for_application_priority],
seems like we can actually customize how these priority integers are
interpret.
2. how do you envision the default value should be interpret? I think this
should probably be a default YARN setting instead of a hard-coded value in
flink-conf.yaml. But I am not sure whether there's a right way to do it. maybe
you can share how Spark does it based on your experience.
Thanks,
Rong
> 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)
