[
https://issues.apache.org/jira/browse/CASSANDRA-12144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382564#comment-15382564
]
Alex Petrov commented on CASSANDRA-12144:
-----------------------------------------
I've renamed {{MergingSStableIterator}} to {{RowMergingSSTableIterator}} and
placed it inside the {{Scrubber}}. Agree this is a better place for it to vbe.
In {{SSTableIdentityIterator}}, I've added a {{doCompute}} method, that
contains just iteration logic, which left {{computeNext}} with all the error
handling, so it deduplicated the code.
Also, the short-circuit within {{doCompute}} that returns {{endOfData()}} is
added.
I'm re-running {{dtests}}. The first run coincided with the 500+ failures, and
second one was made from forked job, so was not very representative. I've run
it through {{upgrade_tests-all-custom_branch_runs}} which should work better,
rebased and re-triggered all CI tests. I'll check results tomorrow, as they'll
presumably run for longer time.
|[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/]|
|[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
(matrix)|https://cassci.datastax.com/view/Upgrades/job/upgrade_tests-all-custom_branch_runs/]|
> 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)
