https://issues.apache.org/jira/browse/CASSANDRA-15898
> Sent: Tuesday, June 23, 2020 at 4:16 PM
> From: "John Doe"
> To: user@cassandra.apache.org
> Subject: Re: cassandra 3.11.4 deadlock
>
>
> Yes
> here is one more example, happended on another node
>
"cassandra"
Subject: Re: cassandra 3.11.4 deadlock
Can you open a JIRA?
https://issues.apache.org/jira/projects/CASSANDRA/issues
On Tue, Jun 23, 2020 at 11:56 AM John Doe
mailto:john@discofan.com]> wrote:We are running
apache-cassandra-3.11.4, 10 node cluster with -Xms32G -X
We are running apache-cassandra-3.11.4, 10 node cluster with -Xms32G -Xmx32G
-Xmn8G using CMS.
after running couple of days one of the node become unresponsive and threaddump
(jstack -F) shows deadlock.
Found one Java-level deadlock:
=
"Native-Transport-Requests-144"
Franc Carter
> One of the projects I am working on is going to need to store about 200TB of
> data - generally in manageable binary chunks. However, after doing some rough
> calculations based on rules of thumb I have seen for how much storage should
> be on each node I'm worried.
> 200TB wit
