bobics
I’m seeing an issue where all the poolboy database workers in our pool are being used after some request load (not a lot) on our server. :poolboy.status/1 shows the state as full. Even when the request load drops, all the poolboy workers are still busy. Error log:
GenServer #PID<0.21289.1135> terminating ** (stop) exited in: :gen_server.call(App.Repo.Pool, {:checkout, #Reference<0.2565884396.2513436674.60058>, true}, 5000) ** (EXIT) time out
In our postgres logs we immediately start seeing, and very few queries going through:
unexpected EOF on client connection with an open transaction
The issue seems similar to Timeouts on Poolboy.checkout · Issue #127 · elixir-ecto/db_connection · GitHub except we’re on OTP 21.0.5 where that bug is already fixed.
We don’t have a specific repro case, except that it seems to occur under some request load. The DB isn’t under any significant load. This typically occurs anywhere from 30 minutes to a few hours, and the request load doesn’t vary significantly during that period as far as I can tell. What’s odd is that the application goes from sub 50ms mean response time to unresponsive almost immediately when the issue occurs, and then never recovers until we restart.
Using Ecto 2.2.10, db_connection 1.1.3
Hoping someone here can provide some leads, thanks!
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #ai
- #elixirconf-us
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
bobics
Did a bunch of debugging today, I think the underlying issue is due to some long running transactions (which don’t get logged properly so we weren’t seeing them in our postgres logs). I’ll update this thread when I confirm.
alexfilatov
hey @bobics , any chance you solved this back in 2019?
thanks!