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


   ## description
   
   In the original design, once the pre-task of a certain task (except for 
conditional nodes and dependent nodes) is completed, as long as the system 
resources are sufficient, the task will be executed immediately. At this time, 
users may not want to perform this task immediately. Now, users can specify a 
task to be executed after a certain delay after being submitted.
   
   My solution for this new feature is: when a task needs to be delayed, the 
worker sleeps for a period of time before the actual execution, and a new 
running state is added to describe the state of the task during this period.
   
   I have considered two options:
   
   - Reach the goal by changing the logic of task timeout
   - Reach the goal by delaying submission
   
   For the first option, the proposal was rejected through community 
discussion. See the mailing list below for the discussion process. As for the 
second solution, because the task itself may wait a long time in the waiting 
queue, and this waiting time is difficult to control and predict, it may happen 
that a long period of time after submission is executed before execution. In 
order to avoid this situation, I decided to implement the delayed execution 
logic in the worker.
   
   
   ## discuss mail list
   
   [[DISCUSS][SUMMER-2020] Time setting of the task 
instance](https://lists.apache.org/thread.html/r4814ea53cb7bc71e6ff2ceabcffdb1af4a70f81b87d5bab0b86a20cf%40%3Cdev.dolphinscheduler.apache.org%3E)
   
   [Discuss on new feature for dependent node 延时等待方案讨论
   
](https://lists.apache.org/thread.html/r32c1f74d4d977de5803d3980f34ec1f55a7328fdf22d109b1f97c9d3%40%3Cdev.dolphinscheduler.apache.org%3E)


----------------------------------------------------------------
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:
[email protected]


Reply via email to