Dusan Malusev

> Reproduced here: https://argus.scylladb.com/tests/scylla-cluster-tests/99aa2ddd-ef8e-402a-b839-d6f9e8e7d1f4 Old version 1.8.6 which has the bug

> [@CodeLieutenant](https://github.com/CodeLieutenant) can you elaborate why it was moved from In Progress to Waiting For Review? Basically it's not seen after 1.8.11 release, so I'll be running a couple of...

Fixed in v1.10.0 https://argus.scylladb.com/tests/scylla-cluster-tests/2152b703-f255-4003-9838-d3b26304e3ac

This is not a bug as update statements are disabled as per this line. https://github.com/scylladb/gemini/blob/master/pkg/generators/statements/mutations.go#L53 I'll enable the updates once the core feature are stable and everything is backported to...

In gemini update statetements are disabled due to issues when validating, before the rewrite, the code is just comented out, after we have validated gemini is behaving ok, we can...

This looks like an issue with retries, since there is a sleep between them. It's really strange that a lot of queries are retried multiple times, and that happens after...

> IIUC below graph, it could have something to do with responses getting bigger and bigger over time: > > > This way validator has more to do (more rows...

@soyacz you are completly right, we are sorting based only on primary keys, and not on clustering, this is not a difficult change, I'll try to do it as soon...

@soyacz We should push this one next, we are already lagging behind the driver releases quite a bit

Even running with 2.1.5, whats the issue here, i dont see it. If something cannot be executed adn gemini sent it to be executed, does not look like a bug...