[
https://issues.apache.org/jira/browse/CASSANDRA-8561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611648#comment-14611648
]
Lyuben Todorov commented on CASSANDRA-8561:
-------------------------------------------
[~nihn] You need to set the log level to WARN for SliceQueryFilter which you've
already done, you also need to have a low enough threshold for tombstones
configured in cassandra.yaml. The setting is `tombstone_warn_threshold` and
default is 1000.
> Tombstone log warning does not log partition key
> ------------------------------------------------
>
> Key: CASSANDRA-8561
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8561
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Environment: Datastax DSE 4.5
> Reporter: Jens Rantil
> Assignee: Lyuben Todorov
> Labels: logging
> Fix For: 2.1.6
>
> Attachments: cassandra-2.1-1427196372-8561-v2.diff,
> cassandra-2.1-1427290549-8561-v3.diff, cassandra-2.1-8561.diff,
> cassandra-2.1-head-1427124485-8561.diff,
> cassandra-trunk-head-1427125869-8561.diff, trunk-1427195046-8561-v2.diff,
> trunk-1427288702-8561-v3.diff
>
>
> AFAIK, the tombstone warning in system.log does not contain the primary key.
> See: https://gist.github.com/JensRantil/44204676f4dbea79ea3a
> Including it would help a lot in diagnosing why the (CQL) row has so many
> tombstones.
> Let me know if I have misunderstood something.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
