Re: java driver with cassandra proxies (option: -Dcassandra.join_ring=false)

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

Re: java driver with cassandra proxies (option: -Dcassandra.join_ring=false)

Hi Stefan, Your analysis is exactly what happen ! 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. * The topology of the cassandra cluster returned by the contact point with the php driver includes data nodes + proxy

Re: java driver with cassandra proxies (option: -Dcassandra.join_ring=false)

It will use the first contact point to connect to the database and once connected, it will read that peers table, which is empty. Contact points are really just that - contact points. I think it does not mean that all of them will be used in some round-robin fashion or what. They are there just

Re: java driver with cassandra proxies (option: -Dcassandra.join_ring=false)

Just to be clear: - How many of the proxy nodes are you providing as contact points? One of them or all of them? It sounds like you're saying you're passing all of them, and only one is connecting, and the driver is declining to connect to the rest because they're not in system.peers. I'm not

Re: java driver with cassandra proxies (option: -Dcassandra.join_ring=false)

We have tested Stargate and were very disappointed... Originally our architecture was PHP microservices (with FPM) + cassandra proxies. But we were blocked because PHP driver is no more supported. We made tests to keep PHP + stargate but there were many issues, the main one (but not the only

Re: java driver with cassandra proxies (option: -Dcassandra.join_ring=false)

Those nodes are not in the peers table(s) because you told them NOT to join the ring with `join_ring=false` so it is working by design. I'm not really sure what you're trying to achieve but if you want to separate the coordinator functions from the storage then what you probably want is to deploy

Re: java driver with cassandra proxies (option: -Dcassandra.join_ring=false)

I'm not 100% sure, but it's worth trying to disable the token metadata , because the driver needs to read the "system.peers_v2" table for populating the token metadata. On 11/10/2023 19:15,