Israel Fruchter

seems like that in the counter_update command we are **not** setting timeouts beside the EOFs we see timeouts all the way from a certion point ``` scylla-bench -workload=uniform -mode=counter_update -replication-factor=3...

> @fruch shall we try building scylla-bench image with base go image version 1.16 and see if it reproduces? if anyone investing time in reproducing this ones, I think we...

maybe ``` Timeout: 5s ``` isn't enough for this test case ?

> I'm trying to understand if it's a scylla-bench issue, it looks like a gocql issue to me. > @sylwiaszunejko / @dkropachev can you please take a look at this...

> Probably appears having a too big loader load like in the following bug: https://github.com/scylladb/scylla-bench/issues/121 you mean we need a bigger loader ? I would rather collect some of the...

> Not sure if this is still relevant and if it's a tool issue or driver issue. It's from before we had retries configuration in s-b There is nothing to...

@soyacz @roydahan I wonder how much this is needed ? @soyacz are we doing fallback now if capacity reservation fails ? if not, we can postpone this to when we...

@soyacz it reproduce again, on the same master job: https://jenkins.scylladb.com/job/scylla-master/job/longevity/job/longevity-10gb-3h-azure-test/71/

happen again on master run ## Packages ## Issue description - [ ] This issue is a regression. - [ ] It is unknown if this issue is a regression....

@soyacz you still think this is important to fix ?