cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10888) Tombstone error warning does not log partition key
Date Fri, 19 Feb 2016 13:59:18 GMT

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

Benjamin Lerer commented on CASSANDRA-10888:
--------------------------------------------

The patches look good to me. Just waiting for CI results. 

> Tombstone error warning does not log partition key
> --------------------------------------------------
>
>                 Key: CASSANDRA-10888
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10888
>             Project: Cassandra
>          Issue Type: Improvement
>         Environment: DSE 4.8.2
>            Reporter: Ole Pedersen
>            Assignee: Brett Snyder
>         Attachments: 10888-2.1.txt, 10888-2.2-V2.txt, 10888-2.2.txt
>
>
> Log partition key if read fails due to the ERROR threshold on read tombstoned cells.
> Right now I can specify a warning and an error threshold for C* when reading from a partition
with many tombstones.
> If the query reads more than the “warning threshold” then C* writes a warning to
the log with the partition key.
> But if a query reads more than the “error threshold” then C* aborts the query and
writes to the log – but not the partition key, this time. 
> What I am missing is: Could C* also please write the partition key in case of query abort
due to tombstones?



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

Mime
View raw message