connection_validator not recovering from errors #1971
HoneyryderChuck
started this conversation in
General
Replies: 1 comment 2 replies
-
I've looked into this a bit further, and am applying the It was a bit unclear to me why such a lenient timeout (1 hour seems very long) was chosen as the default, but then again, my judgement may be clouded by today's experience, and the documentation was pretty clear about the alternative (I just overlooked it). |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi 👋 ,
I'm using the "connection_validator" plugin on this AWS setup, where the connection from the ruby processes to the database has an SSL proxy in the middle. My naive interpretation of this plugin was that, if a certain class of errors would happen, the connection would be thrashed and replaced by a freshly initiated connection, which is the use case I'd be most looking for (the SSL proxy frequently drops down connections, and reports it back as timed out, errors, or others).
Today we had an incident, where such an error brought the workers down:
This error was not handled by the connection validator and bubbled up. This led me to investigate why the plugin didn't handle it, and from a quick glance, the plugin is handling only timeouts.
Is my assumption correct? If so, what's the best way to implement the recovery strategy that would allow me to recover from such errors, or is there a plugin for that? Or am I wrong, and the "connection_validator" plugin should have worked, but I'm missing some configuration?
Beta Was this translation helpful? Give feedback.
All reactions