SunnyZ-L opened a new issue #5873: URL: https://github.com/apache/dolphinscheduler/issues/5873
**Describe the bug** Selecting Worker grouping while executing a workflow does not take effect - case 1 1. Create a worker group where the IP does not actually exist. 2. Create a new process definition and the task specifies the worker group created in the first step. 3. Execute the workflow and select the worker group with the name default. 4. After the porcess is started, observe that the value of the WORKER_GROUP_ID field of the T_DS_PROCESS_INSTANCE table is the worker group ID selected when the process is executed. 5. Observe that the value of the WORKER_GROUP_ID field of the T_DS_TASK_INSTANCE table is not equal to the worker group ID selected when the process is executed, but to the worker group ID selected when the task is created. 6. Task is always committed successfully and will not execute. - case 2 1. Create a worker group where the IP does not actually exist. 2. Create a new process definition and the task specifies the worker group with the name default. 3. Execute the workflow and select the worker group created in the first step. 4. After the porcess is started, observe that the value of the WORKER_GROUP_ID field of the T_DS_PROCESS_INSTANCE table is the worker group ID selected when the process is executed(-1). 5. Observe that the value of the WORKER_GROUP_ID field of the T_DS_TASK_INSTANCE table is not equal to the worker group ID selected when the process is executed, but to the worker group ID selected when the task is created(-1). 6. In this case, the worker selection is correct because the following `org.apache.dolphinscheduler.dao.ProcessDao#getTaskWorkerGroupId` code judges `taskWorkerGroupId> 0`, which takes the value of the WORKER_GROUP_ID field of the T_DS_PROCESS_INSTANCE  **Which version of Dolphin Scheduler:** - [1.2.1] -- 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]
