Thank you for the update, Patrick. Appreciate all the work your team, the
community and the Linux Foundation Events team have done. Looking forward
to the virtual event and Cassandra Day series.
> If you have open positions, call them out in this email thread or
#cassandra in the ASF slack.
Speak
*Hello Cassandra Community,We all see what’s happening in tech right now.
Cuts are being made, and budgets are frozen. For Cassandra Summit, this has
translated to low sponsorship and registrations. The program committee has
been discussing options with the Linux Foundation events team, and the
dec
Thank you Sean. I had to remove two of the files and then it started.
Cheers!
-Joe
On 2/3/2023 3:52 PM, Durity, Sean R via user wrote:
In most cases, I would delete the corrupt commit log file and restart.
Then run repairs on that node. I have seen cases where multiple files
are corrupted a
In most cases, I would delete the corrupt commit log file and restart. Then run
repairs on that node. I have seen cases where multiple files are corrupted and
it is easier to remove all commit log files to get the node restarted.
Sean R. Durity
From: Joe Obernberger
Sent: Friday, February 3, 20
Hi all - cluster had a power outage and one of the nodes in a 14 nodes
cluster isn't starting with:
DEBUG [MemtableFlushWriter:1] 2023-02-03 13:52:45,468
ColumnFamilyStore.java:1329 - Flushed to
[BigTableReader(path='/data/2/cassandra/data/doc/correlation_counts-ca4e8c0080b311edbd6d4d9b3bfd78b
