Thanks Patrick!!
On Wed, Jun 30, 2021, 7:54 PM Patrick McFadin wrote:
> Hi Abdul,
>
> This is a release candidate so what the project is proposing as production
> ready. We're asking the community to test however possible and provide any
> feedback you have. If there are no issues found, this
Hi Abdul,
This is a release candidate so what the project is proposing as production
ready. We're asking the community to test however possible and provide any
feedback you have. If there are no issues found, this will turn into the GA
release.
Patrick
On Wed, Jun 30, 2021 at 1:09 PM Abdul
Looks like it's doing a lot of reads immediately on startup
(AbstractQueryPager) which is potentially causing a lot of GC (guessing
that's what caused the StatusLogger).
DEBUG [SharedPool-Worker-113] 2021-06-30 13:39:04,766
AbstractQueryPager.java:133 - Remaining rows to page: 2147483646
is
Downloading now! Thank you! yum update cassandra!
-Joe
On 6/30/2021 3:55 PM, Patrick McFadin wrote:
Congrats to everyone that worked on this iteration. If you haven't
looked at the CHANGES.txt there were some great catches in RC1. Just
like it should happen!
On Wed, Jun 30, 2021 at 12:29
Great news!!
Is this production ready?
On Wed, Jun 30, 2021, 3:56 PM Patrick McFadin wrote:
> Congrats to everyone that worked on this iteration. If you haven't looked
> at the CHANGES.txt there were some great catches in RC1. Just like it
> should happen!
>
> On Wed, Jun 30, 2021 at 12:29 PM
Congrats to everyone that worked on this iteration. If you haven't looked
at the CHANGES.txt there were some great catches in RC1. Just like it
should happen!
On Wed, Jun 30, 2021 at 12:29 PM Mick Semb Wever wrote:
>
> The Cassandra team is pleased to announce the release of Apache Cassandra
>
The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.0-rc2.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source
I have node in cluster when I start c, the cpu reaches 100% with java
process on top. Within a few minutes, jvm crashes (jvm instability)
messages in system.log and c* crashes.
Once c* is up, cluster average read latency reaches multi-seconds and
client apps are unhappy. For now, the only way out
