[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cassandra-user
Subject:    Re: java driver with cassandra proxies (option: -Dcassandra.join_ring=false)
From:       Regis Le Bretonnic <r.lebretonnic () meetic-corp ! com>
Date:       2023-10-12 23:33:46
Message-ID: CAHJx7WVOQCJFs2SDUuKFzUA-JZD=-i5DzRXM-+hS2NwOVntN+g () mail ! gmail ! com
[Download RAW message or body]

Hi Jeff

Today, we use proxy nodes with php, and we are migrating from php to java.
Our farm of php servers is made of 80 physical servers, all of them having
a local proxy node.

So our cassandra cluster is made of :
- DC1 : 6 data nodes + 40 proxies
- DC2 : 6 data nodes + 40 proxies

During our tests with java, we still have our 80 proxy nodes.
We have defined 4 of them as contact point,  also being in a whitelist
policy.

Le ven. 13 oct. 2023 =C3=A0 01:27, Regis Le Bretonnic <
r.lebretonnic@meetic-corp.com> a =C3=A9crit :

> Hi Stefan,
>
> Your analysis is exactly what happen !
> What I can say is that we are migrating from php to java and the behaviou=
r
> of the php (or cpp) driver is completely different.
>
> * The topology of the cassandra cluster returned by the contact point wit=
h
> the php driver includes data nodes + proxy nodes.
> * The topology of the cassandra cluster returned by the contact point
> with the java driver only includes data nodes and there is a control base=
d
> on system.peers table.
>
> If this helps, proxy nodes are part of gossip and participate to
> handshakes. They can be listed with "nodetool gossipinfo" (but I don't fi=
nd
> a system table having this information)  but they are not listed with
> "nodetool status" and are not registered in system.peers.
>
> The challenge is probably to understand how the php driver achieve to hav=
e
> a full list with proxy nodes.
>

[Attachment #3 (text/html)]

<div dir="ltr">Hi Jeff<br><br>Today, we use proxy nodes with php, and we are \
migrating from php to java.<br>Our farm of php servers is made of 80 physical \
servers, all of them having a local proxy node.<br><br>So our cassandra cluster is \
made of :<br>- DC1 : 6 data nodes + 40 proxies<br>- DC2 : 6 data nodes + 40 \
proxies<br><br>During our tests with java, we still have our 80 proxy nodes. <br>We \
have defined 4 of them as contact point,  

also being in a whitelist policy.<br></div><br><div class="gmail_quote"><div \
dir="ltr" class="gmail_attr">Le  ven. 13 oct. 2023 Ã   01:27, Regis Le Bretonnic \
&lt;<a href="mailto:r.lebretonnic@meetic-corp.com">r.lebretonnic@meetic-corp.com</a>&gt; \
a écrit  :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div \
dir="ltr">Hi Stefan,<br><br>Your analysis is exactly what happen !<br>What I can say \
is that we are migrating from php to java and the behaviour of the php (or cpp) \
driver is completely different.<br><br>* The topology of the cassandra cluster \
returned by the contact point with the php driver includes data nodes  + proxy \
nodes.<br>* The topology of the cassandra cluster returned by  the contact point with \
the java driver only includes data nodes  and there is a control based on \
system.peers table.</div><div dir="ltr"><br>If this helps, proxy nodes are part of \
gossip and participate to handshakes. They can be listed with &quot;nodetool \
gossipinfo&quot; (but I don&#39;t find a system table having this information)   but \
they are not listed with &quot;nodetool status&quot; and are not registered in \
system.peers.</div><div><br>The challenge is probably to understand how the php \
driver achieve to have a full list with proxy nodes.</div></div> </blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread]