Hello Cassandra guru:
We are using Cassandra 4.0.1. I want to understand the meaning of
liveness_info from sstabledump output. The following is a sample output of a
record from sstabledump
{
"partition" : {
"key" : [ "1065", "25034769", "6" ],
"position" : 110384220
},
"rows" :
Do you mean the log4j-over-slf4j-#.jar? If so, please read:
http://slf4j.org/log4shell.html
On 13/12/2021 23:48, Rahul Reddy wrote:
Hello,
I see this jar log4j-over-slf4j-1.7.7.jar does it have any impact on
it? Why that jar is used for ?
On Sat, Dec 11, 2021 at 12:45 PM Brandon
Hello,
I see this jar log4j-over-slf4j-1.7.7.jar does it have any impact on it?
Why that jar is used for ?
On Sat, Dec 11, 2021 at 12:45 PM Brandon Williams wrote:
> https://issues.apache.org/jira/browse/CASSANDRA-5883
>
> As that ticket shows, Apache Cassandra has never used log4j2.
>
>
AFAIK there's nothing special being the first disk in the list. It's
fairly likely that you were just "lucky" that an important part of the
system keysapce was on that disk. It's always a good idea to keep some
spare hardware at hand, because you will never know when will they be
needed.
On
Thank you Bowen. I had the policy set to "best_effort", but as Jeff
pointed out since it was the first disk in the list that failed maybe
that is a special case?
I don't have a spare drive at the moment, so I'll just delete all the
cassandra data on that node and have it rejoin as a new
