-
Notifications
You must be signed in to change notification settings - Fork 610
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
Partition scoped components can register as DiskSpaceUsageListener #9715
Conversation
Before this change, adding and removing a disk space usage listener was implemented directly by the broker context and the partition manager only had a callback to add usage listeners. Since we now want to add partition scoped components as disk space usage listeners directly, the `DiskSpaceMonitor` is made available in the `PartitionTransitionContext`.
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.
🎉 The tests are failing. Looks like just an issue in the test setup.Please take a look. Otherwise LGTM.
80e8023
to
699ddd7
Compare
Thanks @deepthidevaki, fixed the test setup 👍 |
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.
🎉
bors r+ |
Build succeeded: |
Description
Before this change, adding and removing a disk space usage listener was implemented directly by the broker context and the partition manager only had a callback to add usage listeners.
Since we now want to add partition scoped components as disk space usage listeners directly, the
DiskSpaceMonitor
is made available in thePartitionTransitionContext
.I couldn't adjust the
ZeebePartition
to not awkwardly forward thenoDiskAvailable
flag to the stream processor because the StreamProcessor can't be aDiskSpaceUsageListener
itself due to circular dependencies between broker and engine.This unblocks #9625 and closes #9712