ducatore
When the DB closes the connection I have a DBConnection.Error.
I would like in this case to retry the query.
Is it something that could be handle by DBConnection or I have to handle myself?
(My use case is when a DB maintenance is applied by GCP)
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #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.
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
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 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
garrison
There is no retry logic for queries in Ecto/DBConnection as far as I’m aware. The way you retry a query can be pretty implementation-specific so it’s hard to provide a generic interface for that.
Depending on how long the maintenance takes the implementation could be very different. E.g. if the DB was down for half an hour are you sure you still want to run that query? Etc.
ducatore
It’s on GCP so the updated instance is available very quickly.
The issue is just with the established connection.
unaware8150
I’d go the no-so-happy-path and use a circuit breaker pattern for this if I really need to do such thing.
Are you sure there are not alternatives besides running a particular query every X time/retry?
ducatore
Since I’m in an API call context if I do nothing the API returned a 500
unaware8150
but that’s a proper response, no? the server side cannot connect to the DB due to a DB maintenance.
Just thinking out of the box, I’d go with a circuit breaker pattern that makes sure to close the connection if it’s open and try again. You could use something like this: Overview — ExternalService v2.0.0 or implement it yourself, which is also a good exercise from time to time