Tags down


How to get rid of the below message in cassandra logs?

By : Vijin
Date : October 14 2020, 02:21 PM
around this issue I have recently upgraded datastax-enterprise from 4.8.16 to 5.0.15. We are using password authentication in PlainText format. But below message is continuously coming in logs. , You need to set:
code :
    plain_text_without_ssl: allow
block  - block the request with an authentication error
warn   - log a warning about the request but allow it to continue (default)
allow  - allow the request without any warning

Share : facebook icon twitter icon

cassandra - logs to find who did what

By : beastmodejosh
Date : March 29 2020, 07:55 AM
I wish this help you If you're using DataStax Enterprise, you can use Audit Logging for that.

cassandra and vault error logs

By : John Goode
Date : March 29 2020, 07:55 AM
this will help Cassandra cluster is not cross-version compatible, you can not upgrade a node only, you have to upgrade the cluster. This is a common mistake people tend to do, please see this video here it mentiones this problem, also it is very very useful with lots of good info.

Distributed logs in Cassandra

By : viniokar
Date : March 29 2020, 07:55 AM
this will help The choice of storing logs in Cassandra is debatable; as the analysis of that data becomes difficult but doable. ELK (Elastic-Logstash-Kibana) or Splunk are more popular choices for log analysis because of their native "text" search support and dashboards.
Having said that, lets look at the problems in hand

Cassandra query logs and performance

By : isaac
Date : March 29 2020, 07:55 AM
I hope this helps . Tracing isn't just limited to CQL. You could enable the same behavior from Java code as well.
Set the tracing flag on the Statement instance. There are various ways depending on how you build it:
code :
// Setter-based:
Statement statement =
  SimpleStatement.newInstance("SELECT * FROM users WHERE id = 1234").setTracing(true);

// Builder-based:
Statement statement =
  SimpleStatement.builder("SELECT * FROM users WHERE id = 1234").withTracing().build();

How do I fetch sorted logs in Cassandra?

By : user3573018
Date : March 29 2020, 07:55 AM
like below fixes the issue WITH CLUSTERING ORDER BY (time DESC);
Adding this at the end of the table solved the problem for me.
Privacy Policy - Terms - Contact Us © voile276.org