Rolling restart after making DDL changes saves us. We saw this because of race
condition in our app servers, but it could happen for various other reasons
like node overloaded, network etc
Sent from my iPhone
> On Oct 12, 2017, at 3:46 AM, Carlos Rolo wrote:
>
> Which
Got the cluster to converge on same schema by restarting just the one
having different version.
Thanks.
On Thu, Oct 12, 2017 at 2:23 PM, Pradeep Chhetri
wrote:
> Hi Carlos,
>
> Thank you for the reply.
>
> I am running 3.9 cassandra version.
>
> I am also not sure what
Hi Carlos,
Thank you for the reply.
I am running 3.9 cassandra version.
I am also not sure what affect does this have on the applications talking
to the cassandra.
So there is no way to converge the cluster schema version without downtime.
Thank you.
On Thu, Oct 12, 2017 at 2:16 PM, Carlos
Which version are you running? I got stuck in a similar situation (With a
lot more nodes) and the only way to make it good was to stop the whole
cluster, start nodes 1 by 1.
Regards,
Carlos Juzarte Rolo
Cassandra Consultant / Datastax Certified Architect / Cassandra MVP
Pythian - Love your
Hello everyone,
We had some issues yesterday in our 3 nodes cluster where the application
tried to create the same table twice quickly and cluster became unstable.
Temporarily, we reduced it to single node cluster which gave us some relief.
Now when we are trying to bootstrap a new node and add