Repository navigation
Cannot share a single DB connection between a unicorn worker and sentry worker #1808
Description
Activity
i would file this under optimizations. we have many workers with autoscaling and limited DB connections. if sentry could re-use a DB connection if needed instead of requiring a new one that would have a big impact for the number of required connections for largely horizontally scaled applications. even making it optional instead of required would be a win in some cases.
one idea: https://stackoverflow.com/a/26733385
Issue Description
It is not possible to have a single database connection for a process that then reports a sentry error asynchronously without opening an additional connection.
we have an RDS DB with many connections, but also a huge fleet of sidekiq workers that can scale up and down in the thousands. so doubling the connection count requirement is not currently possible.
Reproduction Steps
Create a single unicorn worker with a single DB connection that generates an error to report to sentry.
Expected Behavior
The process reports the error using a single DB connection.
Actual Behavior
The process requires two DB connections to report the error.
Ruby Version
2.6.5
SDK Version
5.3.0
Integration and Its Version
No response
Sentry Config
No response