Skip to content
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

Resets compaction queue max size when config changes #5278

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

keith-turner
Copy link
Contributor

Updates the manager to reset the max size on compaction queues when config changes. In the case where the current data size of the queue exceeds the new configured size the lowest priority jobs are dropped until the size is acceptable.

Updates the manager to reset the max size on compaction queues when
config changes.  In the case where the current data size of the queue
exceeds the new configured size the lowest priority jobs are dropped
until the size is acceptable.
@dlmarion dlmarion added this to the 4.0.0 milestone Jan 24, 2025
@@ -294,10 +294,23 @@ protected void startInternalStateCleaner(ScheduledThreadPoolExecutor schedExecut
ThreadPools.watchNonCriticalScheduledTask(future);
}

protected void startConfigMonitor(ScheduledThreadPoolExecutor schedExecutor) {
ScheduledFuture<?> future =
schedExecutor.scheduleWithFixedDelay(this::cleanUpInternalState, 0, 1, TimeUnit.MINUTES);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this call checkForConfigChanges instead of cleanUpInternalState?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ha, yeah it should good catch. I copied and pasted and changed a few things, but missed that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants