ruanwenjun commented on issue #16759: URL: https://github.com/apache/dolphinscheduler/issues/16759#issuecomment-2459492707
> > We will remove `waiting` strategy in the next version. > > When using a stop strategy, the following issue may occur: After the master node distributes a task to the worker, the worker submits the task to its thread pool for execution and attempts to reply to the master. However, if the master has stopped when the worker tries to reply, the worker will attempt to reconnect to the current master several times before throwing an exception. At this point, the worker may already be executing the task, but since the original master has failed, triggering failover, another master takes over. This raises the question: could this situation lead to duplicate task execution Yes, if the task might be duplicate execute in worker, this is an existing problem, and is same with https://github.com/apache/dolphinscheduler/issues/16481. -- 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]
