[Bug] [server] execute COMPLEMENT_DATA command always missing some ack event

[ruancheng77]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

when I execute COMPLEMENT_DATA task.
For example, 1 to 20. And then some task instances always missing field value(start_time/execute_path/log_path)
I find this is due to missing ack event, but I don't kown why missing.

What you expected to happen

all task instance should to be create success.

How to reproduce

Execute task with COMPLEMENT_DATA and date range is longer and bester.

Anything else

No response

Version

2.0.3

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[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/en-us/community/development/subscribe.html ,Then write the issue URL in the email content and send question to dev@dolphinscheduler.apache.org.

[SbloodyS]

Hi, can you please describe the steps of reproduce this issue? ^_^

[ruancheng77]

1.create a work with shell task(echo some message).
2.Execute work with COMPLEMENT_DATA type(Execution mode: seria and schedule time choose 20 days)
3.Look task log When work done. Always some task is missing log but it is execute success.

[SbloodyS]

Hi, I just tested the serial complement data in 2.0.3-release for 20 days, and I can't reproduce this problem. whitch version you are using?

[ruancheng77]

You need goto task detail and look task log.
Some task missing log.
You can look t_ds_task_instance table records. Some record missing start_time/log_path value, that record just like image show.

[SbloodyS]

@ruancheng77 I can successfully reproduce this problem. The task instance is actually executed successfully, but the log does not save in the t_ds_task_intance, resulting in the failure of query on the UI. I will check this issue. Thank you for your feedback. ^_^

[caishunfeng]

I found that workflowExecuteThread use same processInstance java object to run serial complement, which will dismatch the key and value in global processInstanceMap. So when check processInstanceMap.contain(processInstance.id), it will get the error result you don't want, and skip doing something.