Confusing documentation of timeouts #1671
Labels
Comments
martin-sucha
changed the title
|
Thanks for the report! Indeed the docs don't specify when exactly the timeouts apply. |
martin-sucha
added a commit
to kiwicom/gocql
that referenced
this issue
Feb 1, 2023
martin-sucha
added a commit
to kiwicom/gocql
that referenced
this issue
Aug 28, 2023
Client timeouts need to be higher than server timeouts, so that work does not accumulate on the server with retries. This was not true by default, the gocql default timeout was lower than the Cassandra default timeout. Closes apache#1671 Closes apache#1701
martin-sucha
added a commit
to kiwicom/gocql
that referenced
this issue
Aug 28, 2023
Client timeouts need to be higher than server timeouts, so that work does not accumulate on the server with retries. This was not true by default, the gocql default timeout was lower than the Cassandra default timeout. Closes apache#1671 Closes apache#1701
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Cassandra are you using?
n/a
What version of Gocql are you using?
master branch @ 66ec152
What version of Go are you using?
n/a
What did you do?
n/a
What did you expect to see?
n/a
What did you see instead?
The documentation for Timeout is confusing, as it mentions
ConnectionTimeout. It doesn't say whatTimeoutactually does.The text was updated successfully, but these errors were encountered: