cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (Jira)" <>
Subject [jira] [Updated] (CASSANDRA-15890) Add token to tombstone warning and error log message
Date Mon, 22 Jun 2020 18:07:00 GMT


Brandon Williams updated CASSANDRA-15890:
    Fix Version/s: 4.0

> Add token to tombstone warning and error log message
> ----------------------------------------------------
>                 Key: CASSANDRA-15890
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Observability/Logging
>            Reporter: Venkata Harikrishna Nukala
>            Assignee: Venkata Harikrishna Nukala
>            Priority: Normal
>             Fix For: 3.0.21, 3.11.7, 4.0
> If Cassandra scans too many tombstones while reading a partition, then it prints log
messages with query based on warning/failure thresholds. The token is not printed in the log
message. If tombstones are hurting the instance/replica set, then running force compaction
for the partition ("nodetool compact" using start and end tokens i.e. token -/+ some delta)
is one of the actions taken to recover. In order to find out the token, someone has to manually
connect to cluster and run SELECT TOKEN query. Printing token with the log message helps
to avoid manual effort and execute force compaction quickly.

This message was sent by Atlassian Jira

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

View raw message