TianlinLIAO opened a new issue #5993: URL: https://github.com/apache/dolphinscheduler/issues/5993
I know that the current design is: - worker will execute the task (TaskExecuteThread.java#run) - after task is finished, call back service will send TaskExecuteResponseCommand to master - then master will update the cache, and save the task status into db. (TaskResponseService.java#persist) I wonder why not worker update task instance status after task completes. After worker updates the task status, it still can send rpc request to master to update the cache. And what is the benefit the current design? -- 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]
