How to set pool size

[mojixcoder]

Hey,
I wanted to know how can we explicitly set max pool size in gocql?

I mean changing the number of queries which will be run simultaneously.

We are having 150ms avg response time in our monitoring in client side, but we are seeing 24ms avg read latency in Cassansra exporter. Can it be related to pool size?

EDIT: I think that's the function in Java driver: poolingOptions.setMaxRequestsPerConnection(num). What is the equivalent function in gocql?

[cptdom]

Hey, maybe not related, but when we were migrating to cassandra and tinkering with the gocql client, we saw similar latency difference due to the client not properly discovering all nodes and using the same node as the coordinator node for all the requests, resulting in the requests getting queued on a single node and thus slowing down on the client side. Internally, everything seemed fine.
Note: it was on k8s

[martin-sucha]

Hi!

Just recently scylladb#113 was merged to the ScyllaDB fork. It is not available in gocql/gocql yet.

scylladb#114 is also related.

[mojixcoder]

Hey, maybe not related, but when we were migrating to cassandra and tinkering with the gocql client, we saw similar latency difference due to the client not properly discovering all nodes and using the same node as the coordinator node for all the requests, resulting in the requests getting queued on a single node and thus slowing down on the client side. Internally, everything seemed fine. Note: it was on k8s

How did u understand such problem?

[cptdom]

Hey, maybe not related, but when we were migrating to cassandra and tinkering with the gocql client, we saw similar latency difference due to the client not properly discovering all nodes and using the same node as the coordinator node for all the requests, resulting in the requests getting queued on a single node and thus slowing down on the client side. Internally, everything seemed fine. Note: it was on k8s

How did u understand such problem?

We had metrics which allowed us to see which nodes act as coordinators. Also we had query tracing set on gocql which confirmed it.

[mojixcoder]

Hi!

Just recently scylladb#113 was merged to the ScyllaDB fork. It is not available in gocql/gocql yet.

scylladb#114 is also related.

Do you have any idea when is it going to be available in gocql?