You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2016/07/06 13:19:11 UTC
[jira] [Commented] (CASSANDRA-12144) Undeletable rows after
upgrading from 2.2.4 to 3.0.7
[ https://issues.apache.org/jira/browse/CASSANDRA-12144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364288#comment-15364288 ]
Aleksey Yeschenko commented on CASSANDRA-12144:
-----------------------------------------------
I'm suspecting that upgrading is irrelevant here, you just have high timestamps in those rows, that are in the future, so deletes do not override them with now(). What's the writeTime() on those columns?
> 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
>
> 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.
> user_id | id | since | type
> --------------------+--------------------+--------------------------+------
> 116138050710536192 | 153047019424972800 | null | 0
> 116138050710536192 | 153047019424972800 | 2016-05-30 14:53:08+0000 | 2
> And then deleting it again only removes the new one.
> 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
> 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)