[cassandra output] Mitigate "gocql: no hosts available in the pool" cannot recover without restart #1736
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Converted it to draft, there's still a discussion going on in what would be the best fix, maybe on |
|
This "band-aid" is the only thing that's been avoiding the issue to happen so far. I'll keep an eye on |
|
After a week it's getting stuck again, not in the same place, though. |
mfamador
force-pushed
the
mitigate_gocql_issue
branch
from
05b7e8e
to
0b98374
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To mitigate an issue (apache/cassandra-gocql-driver#915 and apache/cassandra-gocql-driver#831) with
gocqlwhen Cassandra's IP address resolves differently or on some particular network glitches, the session does not recover and there's the need to kill the container to be able to write again, an Observer was introduced to monitor and recreate the session when needed.We're hitting this issue for a while now, and since we're using a custom benthos image with this "band-aid" it never happened again, it's being able to recover by itself.