Dmitry Kropachev

> If the feature requires careful considerations from the library user and some amount of supporting code in user code because of aforementioned problems, is there a point of implementing...

@Bouncheck , I have been thinking about this solution, more I think less I like it. This solution to feed hosts to controll connection when it reconnects looks hacky to...

@Bouncheck , I see that you still use `newQueryPlan` at one particular place, can you please switch to `newControlReconnectionQueryPlan` ``` Queue nodes = context.getLoadBalancingPolicyWrapper().newQueryPlan(); ```

> @Bouncheck , I have been thinking about this solution, more I think less I like it. This solution to feed hosts to controll connection when it reconnects looks hacky...

> > @Bouncheck , I see that you still use `newQueryPlan` at one particular place, can you please switch to `newControlReconnectionQueryPlan` > > ``` > > Queue nodes = context.getLoadBalancingPolicyWrapper().newQueryPlan();...

> I can adjust them, but I don't know if it's worth it Please check last commit and tell if you are ok with it.

These errors: ``` 2025/03/24 17:55:02 error: failed to connect to "[HostInfo hostname=\"10.12.10.15\" connectAddress=\"10.12.10.15\" peer=\"10.12.10.15\" rpc_address=\"10.12.10.15\" broadcast_address=\"\" preferred_ip=\"\" connect_addr=\"10.12.10.15\" connect_addr_source=\"connect_address\" port=9042 data_centre=\"us-east\" rack=\"1c\" host_id=\"95ead47a-461b-4a5b-9e42-d730eb16b0b8\" version=\"v3.0.8\" state=DOWN num_tokens=256]" due to error: gocql:...

> [@dkropachev](https://github.com/dkropachev) > > [#181](https://github.com/scylladb/scylla-bench/pull/181) demonstrates that gocql version change is the cause, can you assign someone to take a closer look at it ? Can you please confirm that...

So probably it is the same issue as https://github.com/scylladb/gocql/issues/444 correct ?

Close as dup https://github.com/scylladb/gocql/issues/444