cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Podkowinski (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-13460) Diag. Events: Add local persistency
Date Thu, 22 Jun 2017 11:24:00 GMT


Stefan Podkowinski updated CASSANDRA-13460:
    Status: Patch Available  (was: In Progress)

Persisting critical events will be enabled by default and hopefully will enable users to provide
additional debugging information along with logs or stacktraces in their bug reports. Please
see the [documentation|]
for an introduction.

The proposed implementation will take care of:
* Creation of system table for storing events
* Allowing to configure certain events to be persisted to system table (enabled for some events
by default)
* Documentation on configuration and querying of events

> Diag. Events: Add local persistency
> -----------------------------------
>                 Key: CASSANDRA-13460
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Observability
>            Reporter: Stefan Podkowinski
>            Assignee: Stefan Podkowinski
> 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. 
> 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