[
https://issues.apache.org/jira/browse/CASSANDRA-8561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14379698#comment-14379698
]
Lyuben Todorov commented on CASSANDRA-8561:
-------------------------------------------
cassandra.yaml is pretty full of all sorts of configuration options, adding
things as minor as this will make it even harder for picking up Cassandra.
Having said that, making it configurable is a good idea, but I'd much rather do
it as a system setting (param at startup, something like
{{{-Dcassandra.tombstone_warn_keylength_max=500}}}) rather than adding it to
cassandra.yaml. [~dbrosius] [~iamaleksey] WDYT?
> 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-1427196372-8561-v2.diff,
> cassandra-2.1-8561.diff, cassandra-2.1-head-1427124485-8561.diff,
> cassandra-trunk-head-1427125869-8561.diff, trunk-1427195046-8561-v2.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)
