[
https://issues.apache.org/jira/browse/CASSANDRA-8561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14287556#comment-14287556
]
Ian Rose commented on CASSANDRA-8561:
-------------------------------------
This would be very useful when debugging. As it is now I generally have to use
timestamps to correlate between C* logs and my app logs to try to figure out
what query triggered the warning. Getting the partition key right from the C*
log would save a lot of time.
> 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
> Labels: logging
> Fix For: 2.1.3, 2.0.13
>
>
> 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)
