[
https://issues.apache.org/jira/browse/CASSANDRA-8561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377665#comment-14377665
]
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: 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,
> cassandra-2.1-head-1427124485-8561.diff,
> cassandra-trunk-head-1427125869-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)
