Radeity commented on PR #14042: URL: https://github.com/apache/dolphinscheduler/pull/14042#issuecomment-1543386940
> But why do we need to make an error in the task and try the task again? If the content of the resource I replaced does not affect the data execution results, but it causes an exception in the task at this time, I think this is a bit unreasonable. If an exception occurs and the task is retried, the operation and maintenance personnel will have to locate the cause of the problem, which undoubtedly increases the workload. I never say we should retry the task... just answer your last question. And my points are clear at the beginning, maybe we should better not introduce this heavy distributed lock. -- 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]
