cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Petrov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12144) Undeletable rows after upgrading from 2.2.4 to 3.0.7
Date Tue, 12 Jul 2016 12:09:20 GMT

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

Alex Petrov commented on CASSANDRA-12144:
-----------------------------------------

Created broken sstables for both 2.0 and 3.0 storage formats and wrote some unit tests to
reproduce the failures and make the review possibly easier.

|[3.0|https://github.com/ifesdjeen/cassandra/tree/12144-3.0] |[utest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12144-3.0-testall/]
|[dtest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12144-3.0-dtest/]
|[upgrade tests|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/upgrade_tests-all-12144-3.0/]|
|[trunk|https://github.com/ifesdjeen/cassandra/tree/12144-trunk] |[utest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12144-trunk-testall/]
|[dtest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12144-trunk-dtest/]
|[upgrade tests|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/upgrade_tests-all-12144-trunk/]|

I'm re-running the tests again (although only changes were my added sstables and tests). 
Unfortunately, upgrade tests are not very representative as they're throwing similar failures
(in similar amounts on [trunk|https://cassci.datastax.com/view/Upgrades/job/upgrade_tests-all/lastCompletedBuild/testReport/]),
also failures look more like assertion mismatches. 

> 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)

Mime
View raw message