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/12/24 04:04:29 UTC

[GitHub] [incubator-dolphinscheduler] Squidyu opened a new issue #4300: [Bug][master] proccess will wait permanently

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


   **For better global communication, Please describe it in English. If you feel the description in English is not clear, then you can append description in Chinese(just for Mandarin(CN)), thx! **
   **Describe the bug**
   When the master gets a process with more than 100(master.exec.threads - activeCount) sub processes, it will wait permanently.
   
   **To Reproduce**
   Steps to reproduce the behavior, for example:
   1. Go to 'Define process A, there are 10 common subprocesses, define a process B, there are 10 processes A'
      定义流程A,里面有10个普通子流程,定义一个流程B里面有10个子流程A
   2. Click on 'run'
    点击运行
   4. See error at process instance list,process B will wait permanently.
   
   **Expected behavior**
   run process B,Keep it running
   
   **Screenshots**
   If applicable, add screenshots to help explain your problem.
   
   **Which version of Dolphin Scheduler:**
    -version:all
   
   **Additional context**
   ![image](https://user-images.githubusercontent.com/22636614/103059242-836e4e80-45df-11eb-931a-0e5f4ea1a639.png)
   ![image](https://user-images.githubusercontent.com/22636614/103059266-8f5a1080-45df-11eb-9cd9-48df1d838998.png)
   
   
   **Requirement or improvement**
   I don't think process B should be directly put into the waiting thread when dividing the main process, otherwise it will never have a chance to run. Maybe when adding a new process, judge the number of subprocesses and give a friendly prompt.
   
   我认为分割主流程时不该直接将process B放入等待线程,否则永远没有机会运行,也许新增流程时判断子流程数量,给出友好提示
   


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