[Question] why not worker update task instance status after task completes

[lightning-L]

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. And I noticed that master is checking task instance table to update the process instance status (MasterExecThread.java#runProcess).
After worker updates the task status, it can still send rpc request to master to update the cache.

And what is the benefit the current design(master update the task instance status)?

[github-actions]

Hi:

• Thank you for your feedback, we have received your issue, Please wait patiently for a reply.
• In order for us to understand your request as soon as possible, please provide detailed information、version or pictures.
• If you haven't received a reply for a long time, you can subscribe to the developer's email，Mail subscription steps reference https://dolphinscheduler.apache.org/zh-cn/community/development/subscribe.html ,Then write the issue URL in the email content and send question to dev@dolphinscheduler.apache.org.

[CalvinKirs]

The worker is responsible for the execution of tasks, does not interact with the database, and is managed by the master to maintain the execution of subsequent tasks

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[geosmart]

the master responsible to interact with database, package the db data with command and send it by netty.
so the worker just need to run the task and return the result.

this is more simple than both master and worker need to interact with db.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[github-actions]

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.