cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lyuben Todorov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8561) Tombstone log warning does not log partition key
Date Mon, 16 Mar 2015 16:36:38 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14363446#comment-14363446
] 

Lyuben Todorov commented on CASSANDRA-8561:
-------------------------------------------

The below is just to outline the format and demoes a simple case using a text PK, the updated
log message should look something like the below (note the addition of *for key: example1*):

{noformat}
WARN [ReadStage:25672] 2015-01-05 11:30:40,144 SliceQueryFilter.java (line 225) Read 1331
live and 30136 tombstoned cells in mykeyspace.mytable for key: example1 (see tombstone_warn_threshold).
... rest of log line.
{noformat}

> 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
>
>
> 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)

Mime
View raw message