apache / apache/cassandra-gocql-driver

Using gocql for integration unit test but failed intermittently

Open
#1,742 3 comments 1 reaction 0 assignees View on GitHub
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?
3.11.4

### What version of Gocql are you using?
1.6.0

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

### What did you do?
I wrote integration unit tests. I wrote data into the tables and read them back for comparison.

### What did you expect to see?
I expected to see the same values

### What did you see instead?
Sometime the data could not be read back (not connection error, my cassandra is localhost) and caused the test to fail. It usually worked if I reran the test suite, but not always. My test suite has 100+ test cases. Sometimes rerun did not pass and failed at diff test cases.

---

If you are having connectivity related issues please share the following additional information

### Describe your Cassandra cluster
please provide the following information

- output of `nodetool status`
- output of `SELECT peer, rpc_address FROM system.peers`
- rebuild your application with the `gocql_debug` tag and post the output

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the intermittent failure in the 100+ integration test suite against Cassandra 3.11.4 and GoCQL 1.6.0. Rebuild with the gocql_debug tag and collect nodetool status plus SELECT peer, rpc_address FROM system.peers as requested; done means identifying a reproducible cause for reads returning unexpected or missing data.

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.