Background is below
1. 3x i3.4xlarge EC22. 3 replicas3. Client use Scylla CQL Driver
Question is:1. If we configure the connection number to 1 on the client side, will all the request route to one fixed ec2 which cause the coordinator inbalance?
No. Drivers will open one connection per node, not one connection
in total. In addition the Scylla shard-aware driver will open one
connection per shard. You can verify this using the monitoring, it
shows how many connections are active, or using the `ss` tool.
2. Is there any tuning method to reduce the impact of write traffic on read?
In Scylla Enterprise you can define different resource shares for
different sessions, and then direct reads and writes into
different sessions [1]. In Scylla open source you can adjust the
client-side concurrency.
[1]
https://docs.scylladb.com/using-scylla/workload-prioritization/
the client default conf is: Protocol version is V4 Pooling options - coreConnectionsPerHostLocal: 1 maxConnectionsPerHostLocal: 1 coreConnectionsPerHostRemote: 1 maxConnectionsPerHostRemote: 1 maxReqPerConnHostLocal: 1024 maxReqPerConnHostRemote: 256
--
You received this message because you are subscribed to the Google Groups "ScyllaDB users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-users/73f75d95-52db-4066-af16-51fb23ae6618n%40googlegroups.com.