apache / apache/cassandra-gocql-driver

Default timeout in gocql.query

Open
#1,674 3 comments 0 reactions 0 assignees View on GitHub
question
Dominant language
Go
Stars
2.7k
Forks
658
PR merge metrics
No merged PRs in 30d

Description

Please answer these questions before submitting your issue. Thanks!

### What version of Cassandra are you using?
I am using apache keyspaces

### What version of Gocql are you using?
v0.0.0-20200131111108-92af2e088537

### What version of Go are you using?
1.16

### What did you do?
When I am trying to write some data to keyspaces I am getting this below error::
"error":"Operation timed out - received only 0 responses.",
The thing is I know why I am getting this error. because all keyspaces nodes are busy..
I have set the session timeout to 10 s. I am not able to set the write Timeout because I am using older version of gocql. Could you please tell me what is the default write timeout in this older version of golang and if possible point to code as well or dcoumentation for proof..

Some more details:
how my query look like,
gocqlx.Query(ts.Session.Query(fmt.Sprintf(ts.stmts[insertTags], buildTableName(tagsTable, zoneId))), ts.names[insertTags]).
Bind(vals...).
ExecRelease()

Thanks

Contributor guide

Open the contributing guide

Research direction

Start by tracing the gocqlx.Query(...).Session.Query(...).ExecRelease() path in the reported GoCQL version and locate how query and session timeouts are selected. Confirm the default write timeout from the implementation or documentation, then document the finding and how it applies to the reported Apache Keyspaces error.

Written by the indexing model from the issue text.

Assessment

Tech stack
cassandra, go
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.