cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Podkowinski (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13460) Diag. Events: Add local persistency
Date Tue, 10 Apr 2018 08:24:00 GMT


Stefan Podkowinski commented on CASSANDRA-13460:

The proposed solution should be reconsidered using the chronicle queue based BinLog, instead
of writing to a local keyspace. This should be a better solution for storing temporary, time
based and sequentially retrieved events. We also get better portability by being able to simply
copy already rolled over log files and read them on external systems. E.g. you could ask a
user to enable diag event logging for compactions and have him send you an archive with all
bin logs the next day, just by working with files.

> Diag. Events: Add local persistency
> -----------------------------------
>                 Key: CASSANDRA-13460
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Observability
>            Reporter: Stefan Podkowinski
>            Assignee: Stefan Podkowinski
>            Priority: Major
> Some generated events will be rather less frequent but very useful for retroactive troubleshooting.
E.g. all events related to bootstraping and gossip would probably be worth saving, as they
might provide valuable insights and will consume very little resources in low quantities.
Imaging if we could e.g. in case of CASSANDRA-13348 just ask the user to -run a tool like
{{./bin/diagdump BootstrapEvent}} on each host, to get us a detailed log of all relevant events-
 provide a dump of all events as described in the [documentation|].

> This could be done by saving events white-listed in cassandra.yaml to a local table.
Maybe using a TTL.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message