[GitHub] [dolphinscheduler] caishunfeng commented on pull request #12636: [Bug] [API]After we delete the worker group, but this task group still keep in the task setting.

[GitBox <gi...@apache.org>]

caishunfeng commented on PR #12636:
URL: https://github.com/apache/dolphinscheduler/pull/12636#issuecomment-1299535999

   > I don't think this PR has solved this problem, the history version may still use the worker group. And we don't need to do these check, once the master cannot find the worker group, the task need to fail, rather than still retry. cc @SbloodyS @caishunfeng
   
   Yes, the history version may still use the worker group, but if we don't check for the current version, it will cause execute fail, I think it's not users want.
   If we check for the current version, when user switch workflow version, is it better try to check all dependent resources and give some tips? WDYT?


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org