That text would be a wonderful improvement. Thank you…
Regards,
Sean
From: Mick Semb Wever
Reply-To: "user@cassandra.apache.org"
Date: Monday, January 31, 2022 at 4:10 PM
To: "user@cassandra.apache.org"
Subject: Re: 4.1 Release Date
Apache Cassandra 3.0
Released on
>
> Apache Cassandra 3.0
> Released on 2021-02-01, and supported until 4.1 release
> (April 2022).
>
Would the wording "… and supported until 4.1.0 release (May-June 2022)." be
enough?
(it would be nice to keep the text brief on this page)
If you would like to…
this is th
Once again it was related to hostname configuration (I remember had problem
with this multiple times before even on different applications), this time the
root cause was a typo in one of multiple config files for hostname (different
name on /etc/hostname with /etc/hosts)! I fixed that and now th
Since 3.x worked and 4.x didn't, it is most likely caused by clock out
of sync between servers. Cassandra 3.x by default has cross node timeout
disabled, and Cassandra 4 has changed the default to enabled. Check the
system time on both servers are accurate. Use NTP to prevent this from
happenin
TP stats indicate pending gossip. Check that the times are synchronised on
both nodes (use NTP) since it can prevent gossip from working.
I'd also suggest looking at the logs on both nodes to see what other WARN
and ERROR messages are being reported. Cheers!
Hi,
I'm trying to setup a Cluster of apache Cassandra version 4.0.1 with 2 nodes:
1. on node1 (192.168.1.1), extracted tar.gz and config these on yml:
- seeds: "192.168.1.1"
listen_address: 192.168.1.1
rpc_address: 192.168.1.1
2. started node1 and a few seconds later it is UN
3.on
Michael,
Thank you very much, that level of detail is what I was hoping to get. From
your response, it sounds as though a formal 4.1.x release would not be before
May and there is an excellent chance it would be June or later. May I ask that
the info posted on the Downloads page get an update
