ClosedChannelException is often the result of a network connectivity
issue. It's worth check the OS logs and the configuration of network
devices between the nodes. For example, has the conntrack table filled
up? Does any router between the two nodes have short TCP session timeout?
A crashed p
Thank you Bowen. Adding more nodes, but the latest one keeps failing.
On the node being added:ERROR
[Stream-Deserializer-/192.168.115.187:7000-83045bad] 2024-08-15
21:08:08,315 CassandraEntireSSTableStreamReader.java:146 - [Stream
59fa6610-5b48-11ef-8ffc-a13bcc763c65] Error while reading ssta
Also I just wanted to point out that there is a cassandra-drivers slack room on
the ASF slack where folks that work on the different drivers interact.
(added to both user and dev list thread)
> On Aug 14, 2024, at 5:59 PM, Dinesh Joshi wrote:
>
> Hi Vincent,
>
> This is the Cassandra user's m
You may need to look at the zipped log files if the streaming had been
running for a while before failing. The error could have happened hours
or days before the final failure.
If your cluster is already experiencing performance issues (e.g. due to
CPU bottleneck or GC pauses), it's highly lik
Thank you Bowen - yeah the only ERROR I see in
/var/log/cassandra/debug.log is:
ERROR [main] 2024-08-15 04:48:23,374 StorageService.java:2041 - Error
while waiting on bootstrap to complete. Bootstrap will have to be restarted.
java.util.concurrent.ExecutionException:
org.apache.cassandra.strea
