You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Lyuben Todorov (JIRA)" <ji...@apache.org> on 2015/03/17 11:04:39 UTC

[jira] [Updated] (CASSANDRA-8561) Tombstone log warning does not log partition key

     [ https://issues.apache.org/jira/browse/CASSANDRA-8561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lyuben Todorov updated CASSANDRA-8561:
--------------------------------------
    Attachment: cassandra-2.1-8561.diff

> 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.4
>
>         Attachments: cassandra-2.1-8561.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)