Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 7 May 2015 19:57:00 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12828076.1431023292000.40090.1431028620191@Atlassian.JIRA>
In-Reply-To: <JIRA.12828076.1431023292000@Atlassian.JIRA>
References: <JIRA.12828076.1431023292000@Atlassian.JIRA>
 <JIRA.12828076.1431023292756@arcas>
Subject: [jira] [Commented] (CASSANDRA-9326) Seeing tombstone warning
 message
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aleksey Yeschenko commented on CASSANDRA-9326:
----------------------------------------------

{{localDeletion=2147483647}} ({{Integer.MAX_VALUE}}) here only means that there is no partition level deletion here.

The reasons you see that warning are that 1) compaction hasn't yet compacted them all away and 2) the way the column counter works. CASSANDRA-9326 is open to handle the latter, and you'll have to deal with the former.

> Seeing tombstone warning message
> --------------------------------
>
>                 Key: CASSANDRA-9326
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9326
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: srinivasu gottipati
>            Priority: Minor
>             Fix For: 2.0.x
>
>
> We deleted data for some of the rows in one of the column families. 
> After that we ran repair on all nodes, and followed by reducing gc_grace_seconds that way compaction can remove all the tombstones upon expiry of gc_grace_seconds time. 
> When we are querying the data now, seeing the following errors:
> WARN [ReadStage:1142] 2015-05-06 17:50:53,602 SliceQueryFilter.java (line 231) Read 1 live and 1487 tombstoned cells in XXXX (see tombstone_warn_threshold). 10001 columns was requested, slices=[-], delInfo={deletedAt=-9223372036854775808, localDeletion=2147483647} 
> We deleted this data while back and for sure gc_grace_seconds is elapsed long time back and we use leveled compaction. In the above, errors, localDeletion points to some time in future (MAX INT VALUE) and that could be the reason these are n't being purged. Any help (or) workaround is appreciated.


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