Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 22 Jan 2015 21:22:34 +0000 (UTC)
From: "Robert Coli (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12764901.1420463537000.150696.1421961754831@Atlassian.JIRA>
In-Reply-To: <JIRA.12764901.1420463537000@Atlassian.JIRA>
References: <JIRA.12764901.1420463537000@Atlassian.JIRA>
 <JIRA.12764901.1420463537142@arcas>
Subject: [jira] [Commented] (CASSANDRA-8561) Tombstone log warning does not
 log partition key
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Coli commented on CASSANDRA-8561:
----------------------------------------

I'd like it if this warning (and/or tracing output) had a concept of "shadowed" columns independent from "tombstones." I am likely to file a ticket on the tracing output improvement, but IMO having a ton of shadowed columns is just as bad as having a bunch of tombstones, and we should warn here in both cases?

> 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
>              Labels: logging
>             Fix For: 2.1.3, 2.0.13
>
>
> 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)