[
https://issues.apache.org/jira/browse/CASSANDRA-12144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364833#comment-15364833
]
Stanislav Vishnevskiy commented on CASSANDRA-12144:
---------------------------------------------------
Yup for some rows somehow it manages to have multiple rows for the same primary
key. Only old rows it seems that existed prior to the upgrade.
We followed the steps outlines in this document.
https://docs.datastax.com/en/latest-upgrade/upgrade/cassandra/upgrdBestPractCassandra.html
Which included running upgradesstables before and after the upgrade.
> 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.
> {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)
