[
https://issues.apache.org/jira/browse/FLINK-27550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-27550:
-----------------------------------
Labels: auto-deprioritized-major pull-request-available (was:
pull-request-available stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Major, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Remove checking yarn queues before submitting job to Yarn
> ---------------------------------------------------------
>
> Key: FLINK-27550
> URL: https://issues.apache.org/jira/browse/FLINK-27550
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Reporter: Junfan Zhang
> Priority: Minor
> Labels: auto-deprioritized-major, pull-request-available
>
> When invoking the method of {{checkYarnQueues}} in YarnClusterDescriptor,
> it will check the specified yarnQueue whether exists in the queues gotten by
> the YarnClient.QueueInfo.
> However when using the capacity-scheduler, the yarn queues path should be
> retrieved by the api of {{QueueInfo.getQueuePath}}
> instead of {{getQueueName}}.
> Due to this, it will always print out the yarn all queues log, but it also
> can be submitted to Yarn successfully.
> The api of getQueuePath is introduced in the latest hadoop
> version(https://issues.apache.org/jira/browse/YARN-10658), so it's hard to
> solve this problem in the older hadoop cluster.
> According to the above description, the process of checking is unnecessary.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
