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

Callbacks for blocked/unblocked notifications #43

Merged
merged 1 commit into from
Mar 9, 2024

Conversation

carlhoerberg
Copy link
Member

When the server is out of disk or RAM it might notify its clients. Prevoiusly we blocked all writes but that also made it impossible to send Ack/Reject frames when consuming for instance, which made so that the server might not recoup disk space or RAM when the queue was shrinking.

Connection#on_blocked and Connection#on_unblocked callbacks are now added so that the user can stop only publishing when the server is blocked.

When the server is out of disk or RAM it might notify its clients.
Prevoiusly we blocked all writes but that also made it impossible to
send Ack/Reject frames when consuming for instance, which made so that
the server might not recoup disk space or RAM when the queue was
shrinking.

Connection#on_blocked and Connection#on_unblocked callbacks are now
added so that the user can stop only publishing when the server is
blocked.
@carlhoerberg carlhoerberg merged commit 631652f into main Mar 9, 2024
3 checks passed
@carlhoerberg carlhoerberg deleted the blocked-unblocked branch March 9, 2024 10:00
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.

1 participant