You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2020/07/31 01:40:55 UTC

[GitHub] [incubator-dolphinscheduler] BoYiZhang opened a new issue #3361: [Question] Why are the yarn queue properties now stored on the user / tenant table

BoYiZhang opened a new issue #3361:
URL: https://github.com/apache/incubator-dolphinscheduler/issues/3361


   The queue field was previously specified when the workflow was defined
   
   Why is it stored on users / tenants now
   
   What are the considerations?
   
   
   ---------------------------------------------
   
   There will be multiple yarn queues. It is possible that when a user creates a task, it will be submitted to multiple queues of yarn
   
   @dailidong 
   
   
   ![image](https://user-images.githubusercontent.com/39816903/88990719-4ee8b600-d311-11ea-8beb-3cb511fbad6e.png)
   
   
   
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [incubator-dolphinscheduler] BoYiZhang closed issue #3361: [Question] Why are the yarn queue properties now stored on the user / tenant table

Posted by GitBox <gi...@apache.org>.
BoYiZhang closed issue #3361:
URL: https://github.com/apache/incubator-dolphinscheduler/issues/3361


   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org