Re: Node failed after drive failed

Likely lost (enough of) the system key space on that disk so the data files indicating the host was in the cluster are missing and the host tried to rebootstrap > On Dec 11, 2021, at 12:47 PM, Bowen Song wrote: > >  > Hi Joss, > > To unsubscribe from this mailing list, please send an

Re: Node failed after drive failed

Hi Joss, To unsubscribe from this mailing list, please send an email to user-unsubscr...@cassandra.apache.org, not the mailing list itself (user@cassandra.apache.org). On 09/12/2021 16:14, Joss wrote: unsubscribe On Mon, 6 Dec 2021 at 14:12, Joe Obernberger wrote: Hi All - one node

Re: Node failed after drive failed

Hi Joe, In case of a single disk failure, you should not remove the data directory from the cassandra.yaml file. Instead, you should replace the failed disk with a new empty disk. See https://docs.datastax.com/en/cassandra-oss/3.x/cassandra/operations/opsRecoverUsingJBOD.html for the steps.

Re: Log4j vulnerability

https://issues.apache.org/jira/browse/CASSANDRA-5883 As that ticket shows, Apache Cassandra has never used log4j2. On Sat, Dec 11, 2021 at 11:07 AM Abdul Patel wrote: > > Hi all, > > Any idea if any of open source Cassandra versions are impacted with log4j > vulnerability which was reported on

Re: Log4j vulnerability

As far as I can tell, cassandra uses logback, not log4j2, so it shouldn't be affected. The logback website , in fact, now has some quite snarky language differentiating it from log4j2. On Sat, Dec 11, 2021 at 9:07 AM Abdul Patel wrote: > Hi all, > > Any idea if any of

Log4j vulnerability

Hi all, Any idea if any of open source Cassandra versions are impacted with log4j vulnerability which was reported on dec 9th