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: https://issues.apache.org/jira/browse/CASSANDRA-13460
>             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|https://github.com/spodkowinski/cassandra/blob/WIP-13460/doc/source/operating/diag_events.rst].
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to