Dmitry Kropachev
Dmitry Kropachev
Currently `s-m` does not track topology changes, unless it is doing something on the cluster, then it does the following: ``` hosts, err := s.discoverHosts(ctx, client) if err != nil...
There are limitations that we need to apply in certain cases for restore tasks: 1. No parallel restore tasks running on the same keys pace 2. When restore on the...
Make use of [Query.Observer](https://pkg.go.dev/github.com/gocql/gocql#Query.Observer) on query logging. Biggest problem with it is that currently we use `PrettyCQL`, on our customer data types. So, either we have to glue it with...
on golang `1.21` [PGO](https://go.dev/doc/pgo) was released, and we can make use of it. Just preliminary idea: 1. Before releasing new version we would run it against single node cluster collecting...
When statement fails gemini issues log record that looks like this: ``` {"L":"INFO","T":"2023-07-07T13:33:58.831Z","N":"work cycle.validation_job","M":"Validation failed. Error: unable to load check data from the test store: gocql: expected 2 values send...
It comes from https://github.com/scylladb/gemini/issues/382: ``` {"L":"ERROR","T":"2023-07-07T13:34:21.368Z","M":"failed to apply mutation","attempts":15,"error":"[cluster = oracle, query = 'INSERT INTO ks1.table1 (pk0,pk1,ck0,ck1,col0,col1,col2,col3,col4,col5,col6,col7,col8,col9,col10,col11) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,(?,?,?,?,?),?,?,?) ']: gocql: expected 20 values send got 18","errorVerbose":"gocql: expected 20 values...
https://github.com/scylladb/gemini/blob/c93899e0bdc8993ce3c0a3d50be54df1b7eaf70b/pkg/jobs/gen_mutate_stmt.go#L31-L61 Row deletion should be running on both existing and non-existing records with different ration. We need to split them into different statements type.
Since `gemini` dump all the values into single value list: ``` func (g *Generator) createPartitionKeyValues(r *rand.Rand) []interface{} { var values []interface{} for _, pk := range g.table.PartitionKeys { values =...
Add logging via some library kid of [uber-go/zap](https://github.com/uber-go/zap)
Currently `Warmup` respects `failFast` and fails if there is any error in such case. Let's have separate logic for `Warmup`, it should look at `fail` to `success` percentage and fail...