You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "batmanneverdie (via GitHub)" <gi...@apache.org> on 2023/06/07 06:09:21 UTC
[GitHub] [dolphinscheduler] batmanneverdie commented on issue #14291: [Feature][Worker Group] Adding exclusive worker field for default worker group to exclude the specific worker.
batmanneverdie commented on issue #14291:
URL: https://github.com/apache/dolphinscheduler/issues/14291#issuecomment-1579961643
For the case of creating a new worker group, I think it is not friendly in the following scenarios:
1. At present, DS will select the `default` group by default. I think most users should not care about what worker group is available and what worker group is specific, they just choose the `default` is OK. But if the `default` group contains a specific worker, then each task user needs to consider which worker group to choose. It's unfriendly.
2. The maintainer must know the address of the worker in advance, and then configure the worker group. When the worker expands or modifies the deployment machine, the worker address will change. The operation and maintenance personnel also need to change the worker group, which increases the mental burden.
BTW,I think that in the worker group management UI, the worker should display its active status, such as green for survival, and red for death or non-existence. Currently all display green.
--
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