ORuteMa commented on issue #14251: URL: https://github.com/apache/dolphinscheduler/issues/14251#issuecomment-1578174169
> > Queue at user/tenant level actually take affect as my practice shows in #14237. > > It's weird, do you mean queue of user/tenant can be set to your Flink/Spark task? I don't find where the evaluation takes effect in codes. Would you like to help locate it? > > > Keep queue in task-level can lead to arbitrary use of YARN resources and I think it's the reason for its deprecation. > > You said it inconvenient for user to define queue in task definition page, and we can not avoid this arbitrary usage, cuz user can still define the yarn queue option by themselves. Sorry for my late reply. For example, in FlinkArgsUtils class, you can find the queue is in FlinkParameters, FlinkParameters obtain the queue from ProcessInstance in 3.1.7 branch (User queues have priority over tenant queues). But I find it is miss in dev, so weird! Regrading queue option from task form, maybe we can just ignore them and give a tip. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
