Small correction in cassandra driver usage,
Driver used: Spring boot (
org.springframework.boot:spring-boot-starter-data-cassandra)
Version: 2.3.2.RELEASE
Are there any differences between spring boot (I think it's based on
datastax cql driver) and Datastax core driver load balancing policies?
T
Thanks Erick.
We are using datastax java driver (
https://docs.datastax.com/en/developer/java-driver/).
Driver version number: 3.3.0
C* version: 3.11.6
Regards,
Sandeep
On Sat, Sep 12, 2020 at 2:41 PM Erick Ramirez
wrote:
> That would be my last option to add a new host as contant point but
>
> That would be my last option to add a new host as contant point but as per
> my understanding cassandra should auto discover newly joined nodes and
> server or load balance connections automatically but it's not happening.
>
Yes, that sounds right to me. Sorry, this fell off my radar due to
co
gt; definition) and partitioner is used across nodes ?
>
>
> ~Asad
>
>
>
>
>
>
>
>
>
>
>
> *From:* Sandeep Nethi
>
>
> *Sent:* Tuesday, September 8, 2020 1:12 AM
>
>
> *To:* user@cassandra.apache.org
>
>
> *Subject:* Re: C
Can you share please what replica placement strategy ( in keyspace definition)
and partitioner is used across nodes ?
~Asad
From: Sandeep Nethi
Sent: Tuesday, September 8, 2020 1:12 AM
To: user@cassandra.apache.org
Subject: Re: Cassandra scale-out with no traffic on newly joined nodes
That
That would be my last option to add a new host as contant point but as per
my understanding cassandra should auto discover newly joined nodes and
server or load balance connections automatically but it's not happening.
So, i'm trying to understand what could be the root cause here.
Another problem
Can you add new host as contact points and see if traffic lands on them or
not?
Also you can verify new nodes are added in system.peers of host name which
you are giving as contact points
On Tue, Sep 8, 2020 at 11:27 AM Sandeep Nethi
wrote:
> Yes, all nodes are UN and no issues identified. Infac
Yes, all nodes are UN and no issues identified. Infact i could see some
client connections on new nodes with telnet but not seeing any traffic.
Cassandra version: 3.11.6
Load Balancing policy used is default with no custom policies.
Thanks,
On Tue, Sep 8, 2020 at 5:52 PM Erick Ramirez
wrote:
>
That shouldn't be a problem for the control connection.
I would suggest looking into the load-balancing policy configured on the
driver. Also, are all the new nodes fully up and fully joined the cluster?
>
Thanks Erick.
Just to confirm, my application connection string is using host address
details and not VIP/some other load balancer in between.
So, inorder for my application to successfully establish control connection
and be able to read system related tables to learn about topology
automaticall
If I were to guess I'd say that your app is hitting a hardware/software
load-balancer or DNS VIP or DNS round-robin to get to the cluster and so
it's only routing traffic to the old nodes.
If this is the case, I would recommend you use the built-in load-balancing
policy on the C* drivers instead.
11 matches
Mail list logo
