[
https://issues.apache.org/jira/browse/FLINK-13548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900232#comment-16900232
]
Rong Rong commented on FLINK-13548:
-----------------------------------
Yes. I think setting it to the default YARN priority (of the queue submitting
to) is probably the right way to do. Implementation details on whether to use a
flink conf mapping can be discuss in the PR;
Regarding the values for the priority, I think setting it to a non-negative
number is fine for now. but I was wondering if we need to sanity check the
values against the cluster/queue setting? IMO it is problematic submitting
Flink application using an out-of-range priority number - even YARN interprets
them correctly to the max value, we should at least throw a warning (as this
behavior might not be intended by the user)
> 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)
