-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove FixedCountNodeAllocatorService #17333
Merged
losipiuk
merged 2 commits into
trinodb:master
from
losipiuk:lo/remove-fixed-count-node-allocator
May 9, 2023
Merged
Remove FixedCountNodeAllocatorService #17333
losipiuk
merged 2 commits into
trinodb:master
from
losipiuk:lo/remove-fixed-count-node-allocator
May 9, 2023
Conversation
This file contains 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
linzebing
approved these changes
May 3, 2023
losipiuk
force-pushed
the
lo/remove-fixed-count-node-allocator
branch
from
May 3, 2023 19:04
85286ee
to
b840ae0
Compare
findepi
approved these changes
May 3, 2023
core/trino-main/src/main/java/io/trino/execution/scheduler/NodeSchedulerConfig.java
Show resolved
Hide resolved
@@ -60,7 +59,6 @@ public void testExplicitPropertyMappings() | |||
.put("node-scheduler.splits-balancing-policy", "node") | |||
.put("node-scheduler.optimized-local-scheduling", "false") | |||
.put("node-scheduler.allowed-no-matching-node-period", "1m") | |||
.put("node-scheduler.allocator-type", "fixed_count") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does TestNodeSchedulerConfig pass after first commit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does :)
arhimondr
approved these changes
May 4, 2023
losipiuk
force-pushed
the
lo/remove-fixed-count-node-allocator
branch
from
May 7, 2023 12:39
b840ae0
to
bd7956a
Compare
losipiuk
force-pushed
the
lo/remove-fixed-count-node-allocator
branch
from
May 7, 2023 12:40
bd7956a
to
73762f7
Compare
rebased |
CI : #14277 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release notes
(x) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text: