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

Fail sbuf_send_pending operation if dst socket is closed #652

Merged
merged 1 commit into from
Aug 10, 2022

Conversation

kmichel-aiven
Copy link
Contributor

If the dst socket is closed, sbuf_send_pending will fail but not mark the operation as failed.

It will then retry repeatedly, consuming a lot of CPU until pgbouncer is restarted.

If the dst socket is closed, sbuf_send_pending will fail
but not mark the operation as failed. It will then retry
repeatedly, consuming a lot of CPU until pgbouncer is
restarted.
@petere
Copy link
Member

petere commented Mar 14, 2022

How do you get into that situation? Is that something we can cover with a test case?

@JelteF
Copy link
Member

JelteF commented Mar 14, 2022

I'm not sure how it happens. It doesn't happen often. But when it happens it's really bad. pgbouncer starts using 100% of it's CPU core and starts flooding the logs with errors. The only way to stop it is by restarting it. Please merge this simple workaround for this issue.

@mtuncer
Copy link

mtuncer commented Apr 6, 2022

@petere we are looking forward to this fix

@guybrowne
Copy link

Is this likely to make it into the next release? we started hitting this error in version 1.12 have then updated to 1.16 & 1.17 where we are still experiencing it... its very intermittent.

@JelteF JelteF merged commit b553626 into pgbouncer:master Aug 10, 2022
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.

5 participants