Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 6 Jul 2016 21:38:11 +0000 (UTC)
From: "Stanislav Vishnevskiy (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12987121.1467803221000.41955.1467841091117@Atlassian.JIRA>
In-Reply-To: <JIRA.12987121.1467803221000@Atlassian.JIRA>
References: <JIRA.12987121.1467803221000@Atlassian.JIRA> <JIRA.12987121.1467803221187@arcas>
Subject: [jira] [Commented] (CASSANDRA-12144) Undeletable rows after
 upgrading from 2.2.4 to 3.0.7
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 06 Jul 2016 21:38:13 -0000


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

Stanislav Vishnevskiy commented on CASSANDRA-12144:
---------------------------------------------------

I sent you an email.

> Undeletable rows after upgrading from 2.2.4 to 3.0.7
> ----------------------------------------------------
>
>                 Key: CASSANDRA-12144
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12144
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Stanislav Vishnevskiy
>            Assignee: Alex Petrov
>
> We upgraded our cluster today and now have a some rows that refuse to delete.
> Here are some example traces.
> https://gist.github.com/vishnevskiy/36aa18c468344ea22d14f9fb9b99171d
> Even weirder.
> Updating the row and querying it back results in 2 rows even though the id is the clustering key.
> {noformat}
> user_id            | id                 | since                    | type
> -------------------+--------------------+--------------------------+------
> 116138050710536192 | 153047019424972800 |                     null |    0
> 116138050710536192 | 153047019424972800 | 2016-05-30 14:53:08+0000 |    2
> {noformat}
> And then deleting it again only removes the new one.
> {noformat}
> cqlsh:discord_relationships> DELETE FROM relationships WHERE user_id = 116138050710536192 AND id = 153047019424972800;
> cqlsh:discord_relationships> SELECT * FROM relationships WHERE user_id = 116138050710536192 AND id = 153047019424972800;
>  user_id            | id                 | since                    | type
> --------------------+--------------------+--------------------------+------
>  116138050710536192 | 153047019424972800 | 2016-05-30 14:53:08+0000 |    2
> {noformat}
> We tried repairing, compacting, scrubbing. No Luck.
> Not sure what to do. Is anyone aware of this?


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