-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Add new compaction config and status APIs served by the Overlord #17834
Open
kfaraz
wants to merge
19
commits into
apache:master
Choose a base branch
from
kfaraz:fix_compaction_supervisors
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+2,164
−758
Open
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
a317db0
Add API to get cluster compaction config
kfaraz 006ece9
Return non-null compaction snapshot from scheduler
kfaraz 295deab
Fix test
kfaraz b7a37aa
Use supervisors with an IT
kfaraz d9efc7b
Add delay in IT
kfaraz 872bfb6
Add coverage for FixedIntervalOrderPolicy
kfaraz 179f361
Add some new APIs, allow for smooth transition
kfaraz 406f0c1
Add more compaction APIs
kfaraz b86d286
Re-organize compaction APIs
kfaraz 0e2d40c
Remove unused methods
kfaraz 8ba7720
Cleanup
kfaraz a912201
Fix APIs and dependencies
kfaraz eba67d6
Add tests, handle filters
kfaraz 07f45b2
Fix /status/datasources API
kfaraz 7e33720
Fix up the ITs
kfaraz 43ea46f
Merge branch 'master' of github.com:apache/druid into fix_compaction_…
kfaraz a127f46
Fix and rerun ITs
kfaraz c78595c
Use new APIs in ITs
kfaraz 3cc2efc
Yet another attempt at the fix
kfaraz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
I see that the only case the scheduler stops is if it becomes leader, but would it be better to leave it as the general
start()
and stop()`?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.
I am not sure I follow. Could you please elaborate?
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.
stop()
andstart()
seemed to better names from my understanding.stopBeingLeader()
seems to be tying in the reason for why the scheduler is stopping, but that doesn't need to be part of the interface.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.
Oh, the problem is that
becomeLeader()
andstopBeingLeader()
don't exactly start or stop the scheduler anymore. They just notify the scheduler that something has changed i.e. leadership.In fact,
stopBeingLeader()
just sets a flag and returns. The scheduled job handles the change and stops scheduling further jobs.Also, there are now two separate methods
start()
andstop()
which are associated with lifecycle start and stop.