Dmitry Kropachev

> > Let's cover queryes from `awaitSchemaAgreement`, `querySystemPeers` and `querySystemLocal` > > I was following [scylladb/java-driver#312](https://github.com/scylladb/java-driver/pull/312) and there such queries were not covered. @Bouncheck am I right? It [was not](https://github.com/scylladb/java-driver/blob/9eedcaca09d1bb5bb87452389c1eb9cc1bd9645f/driver-core/src/main/java/com/datastax/driver/core/ControlConnection.java#L1060-L1069)....

> > > > Let's cover queryes from `awaitSchemaAgreement`, `querySystemPeers` and `querySystemLocal` > > > > > > > > > I was following [scylladb/java-driver#312](https://github.com/scylladb/java-driver/pull/312) and there such queries were...

> Hmm, how come we didn't merge it? It will not work when drivers are running on different VMs.

In order for it to work properly all instance of the driver needs to be synchronize when they choose one node over another. Otherwise one client pick first node, another...

Perfect solution would involve server to report back to clients some metrics that would help clients not only see when cluster/shard/host is overloaded, but also understand how big overload is...

Or we can reserve to a solution when clients are syncing with each other via 3rd party service (like redis or scylla)

> Well, in such a case the implementation is partial. We either need to get the real queue from the server. It might be ok to estimate it though but...

@sylwiaszunejko , can you please take another look at it.

@illia-li , could you please rebase

> > ### Move `DbError::can_speculative_retry` out from `DbError` > > It is more of opinion. I don't think that `DbError` should hold it, it is very specific logic, it does...