[
https://issues.apache.org/jira/browse/CASSANDRA-15890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143220#comment-17143220
]
Venkata Harikrishna Nukala commented on CASSANDRA-15890:
--------------------------------------------------------
[~brandon.williams] Thanks for looking into it and for the links :) .
Unit tests and dtests in Circle CI passed for trunk and 3.0, but a SASI index
related test failed for 3.11 which is not related to these changes. Tests
failed in ci-cassandra.apache.org Jenkins build (sorry I've no idea about this
environment, not sure how to re-run/fix). How to proceed further?
> Add token to tombstone warning and error log message
> ----------------------------------------------------
>
> Key: CASSANDRA-15890
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15890
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
