CQL driver discovered pod ip and service ip.

15 views
Skip to first unread message

Cong Guo

unread,
Nov 18, 2021, 1:48:26 AM11/18/21
to ScyllaDB users
Hi I tried to benchmark scylla with YCSB. 
environment:
1. 3x i3.4xlarge node
2. deployed on eks on aws

After I enabled token aware feature as below, I found the returned host ip including 1 pod ip and 2 service ip. But I cannot access the service ip directly. How could I get pod ip list?

===== Using optimized driver!!! =====

Connected to cluster:scylla-cluster-i3

/10.100.3.242 a (service ip)

/10.100.213.114 a (service ip)

/172.16.45.52 a (pod ip)

#################### pods

cong.guo@SNC0071 ads_delivery % k get pod -n $RT -owide|grep scylla                                

scylla-cluster-i3-ap-ads-delivery-a-0                 2/2     Running                 1          37h     172.16.45.52     ip-172-16-45-52.ap-northeast-1.compute.internal     <none>           <none>

scylla-cluster-i3-ap-ads-delivery-a-1                 2/2     Running                 1          37h     172.16.22.140    ip-172-16-22-140.ap-northeast-1.compute.internal    <none>           <none>

scylla-cluster-i3-ap-ads-delivery-a-2                 2/2     Running                 1          36h     172.16.6.117     ip-172-16-6-117.ap-northeast-1.compute.internal     <none>           <none>


####################  services

scylla-cluster-i3-ap-ads-delivery-a-0             ClusterIP      10.100.137.244   <none>                                                                               7000/TCP,7001/TCP,7199/TCP,9042/TCP,9142/TCP,10001/TCP,8000/TCP   14d    statefulset.kubernetes.io/pod-name=scylla-cluster-i3-ap-ads-delivery-a-0

scylla-cluster-i3-ap-ads-delivery-a-1             ClusterIP      10.100.3.242     <none>                                                                               7000/TCP,7001/TCP,7199/TCP,9042/TCP,9142/TCP,10001/TCP,8000/TCP   14d    statefulset.kubernetes.io/pod-name=scylla-cluster-i3-ap-ads-delivery-a-1

scylla-cluster-i3-ap-ads-delivery-a-2             ClusterIP      10.100.213.114   <none>                                                                               7000/TCP,7001/TCP,7199/TCP,9042/TCP,9142/TCP,10001/TCP,8000/TCP   14d    statefulset.kubernetes.io/pod-name=scylla-cluster-i3-ap-ads-delivery-a-2

Cong Guo

unread,
Nov 18, 2021, 1:50:31 AM11/18/21
to ScyllaDB users
Seems operator launch scylla with service ip as the broadcast ip, how can I replace it to pod ip?

root         87  6.5  1.2 17181110624 1589824 ? Sl   Nov16 144:46 /usr/bin/scylla --log-to-syslog 0 --log-to-stdout 1 --default-log-level info --network-stack posix --io-properties-file=/etc/scylla.d/io_properties.yaml --cpuset 0-15 --smp 15 --overprovisioned --listen-address 0.0.0.0 --rpc-address 0.0.0.0 --seed-provider-parameters seeds=10.100.3.242 --broadcast-address 10.100.213.114 --broadcast-rpc-address 10.100.213.114 --alternator-address 0.0.0.0 --alternator-port 8000 --alternator-write-isolation only_rmw_uses_lwt --blocked-reactor-notify-ms 999999999 --prometheus-address=0.0.0.0

Cong Guo

unread,
Nov 18, 2021, 1:51:05 AM11/18/21
to ScyllaDB users
For Service ip, I mean Cluster IP.

Tomas Nozicka

unread,
Nov 18, 2021, 3:10:11 AM11/18/21
to scyllad...@googlegroups.com
Hi Cong,

all the IPs should have come from the same source, please file an issue with
details on https://github.com/scylladb/scylla-operator/issues

Regards,
Tomas
> --
> 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/ad97dc14-58a9-460e-a89c-ac99f3526cfan%40googlegroups.com
> .

Cong Guo

unread,
Nov 18, 2021, 3:27:45 AM11/18/21
to ScyllaDB users
Hi Tomas, will do that. But do you know if there is any method to discover pod ip but cluster ip?
Reply all
Reply to author
Forward
0 new messages