You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
What happened
When master use host-selector: lower_weight and when multiple workers are configured with different host-height values, tasks are not being allocated according to the host-height weights. The configuration parameter seems to be ineffective.However, the actual runtime behavior and the results of the unit tests do not meet expectations.
What you expected to happen
The host-height parameter does take effect under the host-selector mode of lower_weight, which is consistent with the documentation.
master is configured with host-selector set to lower_weight.
Both workers have identical configurations.
The first worker-server is configured with host-weight: 100.
The second worker-server is configured with host-weight: 10.
Search before asking
What happened
When master use host-selector: lower_weight and when multiple workers are configured with different host-height values, tasks are not being allocated according to the host-height weights. The configuration parameter seems to be ineffective.However, the actual runtime behavior and the results of the unit tests do not meet expectations.
What you expected to happen
The host-height parameter does take effect under the host-selector mode of lower_weight, which is consistent with the documentation.
dolphinscheduler-doc
How to reproduce
master is configured with host-selector set to lower_weight.
Both workers have identical configurations.
The first worker-server is configured with host-weight: 100.
The second worker-server is configured with host-weight: 10.
Anything else
No response
Version
dev
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: