Add Advanced Settings in the property panel to allow users assign certain worker nodes for operators.
#3267
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aglinxinyuan
requested changes
Feb 21, 2025
Contributor
There was a problem hiding this comment.
Do we have to manually add "applyManualLocation(baseOp)" to every operator? Is there a way to automatically bypass this step if the operator has only one worker? I think it's even ok to show this option on all operators, and for the operators with only one possible assignment, you only show the one option in the dropdown.
bobbai00
reviewed
Apr 14, 2025
core/amber/src/main/scala/edu/uci/ics/amber/clustering/ClusterListener.scala
Outdated
Show resolved
Hide resolved
...orkflow-operator/src/main/scala/edu/uci/ics/amber/operator/ManualLocationConfiguration.scala
Outdated
Show resolved
Hide resolved
...orkflow-operator/src/main/scala/edu/uci/ics/amber/operator/ManualLocationConfiguration.scala
Outdated
Show resolved
Hide resolved
...orkflow-operator/src/main/scala/edu/uci/ics/amber/operator/ManualLocationConfiguration.scala
Outdated
Show resolved
Hide resolved
core/workflow-operator/src/main/scala/edu/uci/ics/amber/operator/PythonOperatorDescriptor.scala
Outdated
Show resolved
Hide resolved
.../workflow-operator/src/main/scala/edu/uci/ics/amber/operator/aggregate/AggregateOpDesc.scala
Show resolved
Hide resolved
bobbai00
changed the title
Advanced Settings section to enable users assign certain worker nodes for operators.
bobbai00
changed the title
Advanced Settings section to enable users assign certain worker nodes for operators.Advanced Settings in the property panel to allow users assign certain worker nodes for operators.
Contributor
|
We will continue investigating this issue later, after we agree on the design of the "Execution Env". |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request enables users to assign certain operators (except for source operators) to a specific computing node. The configuration is located under the operator’s Advanced Settings. Two new properties are introduced:
Defaults to true.
When true, the system uses the existing round-robin mechanism to automatically assign a computing node address.
When set to false, the user can manually specify a computing node address.
Only visible when autoSelectNodeAddress is set to false.
Displays a dropdown of all available node addresses for the user to choose from.
This feature allows for more flexible control over where operators run within the cluster