Dmitry Kropachev

> Its not really something to fix on the driver side, right? Printing a log is not a bug. +1, dtest should not be that fragile, driver does lot's ot...

> Also this print is meaningless and doesn't need to be info, seems like it's a leftover from some debugging session True, I have created pr to lower it down...

Currently blocked by https://github.com/scylladb/gocql/issues/336

> > How do you know what is the driver's speculative read timeout? It probably depends on its internal read timeout which we also do not know. > > @gleb-cloudius,...

> > golang, python, java-3.x - have this problem. java-4.x and rust driver does not have it. > > But I think having speculative retry on heavy queries with big...

> > > Now we should make sure that drivers handle the error properly (speculate on failure if speculation is configured) and then we can remove the hack all together...

> > > > > Now we should make sure that drivers handle the error properly (speculate on failure if speculation is configured) and then we can remove the hack...

> > > > > > > Now we should make sure that drivers handle the error properly (speculate on failure if speculation is configured) and then we can remove...

To be done after https://github.com/scylladb/alternator-load-balancing/issues/14

> the same also on https://jenkins.scylladb.com/job/enterprise-2024.2/job/next/156/testReport/junit/replace_address_test/TestReplaceAddress/Build___x86___dtest_with_topology_changes___test_replace_with_background_workload_use_endpoint_rbo_disabled_/ gw4 [logs-full.release.zip](https://github.com/user-attachments/files/17451788/logs-full.release.004.1.zip)