cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lyuben Todorov (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8561) Tombstone log warning does not log partition key
Date Tue, 24 Mar 2015 10:50:53 GMT


Lyuben Todorov commented on CASSANDRA-8561:

[~dbrosius] Not with the current patch implementation. I guess the concern is geared towards
spamming the logs with massive outputs of keys rather than memory consumption. Since this
is an edge case that shouldn't occur often it shouldn't be a big worry to leave a large log
line in there, but it won't be practical. So now we have a choice, display only part of they
key if the key is larger than size N or don't display the key at all if it's larger than size
N. I'll update the patches to include the former. 

> Tombstone log warning does not log partition key
> ------------------------------------------------
>                 Key: CASSANDRA-8561
>                 URL:
>             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, cassandra-2.1-head-1427124485-8561.diff,
> AFAIK, the tombstone warning in system.log does not contain the primary key. See:
> 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

View raw message