You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Soumava Ghosh (JIRA)" <ji...@apache.org> on 2015/11/11 10:25:11 UTC

[jira] [Commented] (CASSANDRA-10211) SliceQueryFilter warnings should print the partition key

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

Soumava Ghosh commented on CASSANDRA-10211:
-------------------------------------------

Looks like the warning path was fixed as a part of CASSANDRA-8561. The patch attached here is for the tombstone failure path. 
Also adding a null check before logging the Decorated key, which can be null as in RowDataResolver.resolveSuperset().

> SliceQueryFilter warnings should print the partition key
> --------------------------------------------------------
>
>                 Key: CASSANDRA-10211
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10211
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Soumava Ghosh
>            Assignee: Soumava Ghosh
>            Priority: Minor
>             Fix For: 2.1.x
>
>         Attachments: 10211-2.1.txt
>
>
> Currently the SliceQueryFilter does not log the partition key while logging the warning/error when the number of tombstones exceed the limits set by the tombstone_warn_threshold and the tombstone_failure_threshold. Logging the partition key would be really helpful for debugging.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)