[
https://issues.apache.org/jira/browse/CASSANDRA-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264898#comment-14264898
]
Philip Thompson commented on CASSANDRA-8558:
--------------------------------------------
{code}
22e18f5a348a911f89deed9f9984950de451d28a is the first bad commit
commit 22e18f5a348a911f89deed9f9984950de451d28a
Author: Jonathan Ellis <[email protected]>
Date: Mon Dec 2 13:07:28 2013 -0600
Multithreaded commitlog
patch by Benedict Elliot Smith; reviewed by jbellis for CASSANDRA-3578
:100644 100644 6efbfbcfcdf6154901515af6773b2506f0c01cf6
bb3a98a3c9901496ddefcf86aed65b34c948d86d M CHANGES.txt
:040000 040000 11cf0d09242214f03de546dd5af8c7c38f626089
50d2eeff23bb7135387f09bfe21e3d92d85fe2c2 M src
:040000 040000 c521f53214555abc46a9b6b766a2787d9e4b0755
fc1c5f1ab579c49f53be9a50b98aee0a937ba022 M test
{code} is the first commit where the test stops passing, but it is timing out
when dropping space2.table1, it is not making it to the assert.
I have now seen this error in the logs when running the test: {{ERROR
[MigrationStage:1] 2015-01-05 13:33:48,087 CommitLogSegmentManager.java:309 -
Failed waiting for a forced recycle of in-use commit log segments}}
{code}
4b54b8acd21999ad4394feb93deb7cca1de445c0 is the first bad commit
commit 4b54b8acd21999ad4394feb93deb7cca1de445c0
Author: Jonathan Ellis <[email protected]>
Date: Thu Jan 30 17:08:46 2014 -0600
remove Table.switchlock and introduce o.a.c.utils.memory package
patch by Benedict Elliott Smith; reviewed by jbellis for CASSANDRA-5549
:100644 100644 de477aadf9d1893cf4ee716501566f3524c7bc8b
a0338747c2faabdddd5751fd3e598ebb7cefebb3 M build.xml
:040000 040000 6a25b19597fd53e0e0f9e87cf7932fff9bed291d
5dc978748e1edb11a7c422c7b6ae6c807b6aef3c M conf
:040000 040000 72b9515eed1738bde3b557449ffde734e3f01f9c
860751f996ccb315eac621386010c6f9cc28b4a6 M lib
:040000 040000 7439706601eebd2cf74fb8bfd453023de01b6e22
a40c4e4d537df88308cf4669beef8a60a0f52412 M src
:040000 040000 def7eaf6366d75ed03ccaddeb7c5b7f173ae1374
b404d22ed0f571244922530772a4ca56e815de9f M test
{code} is the first commit where the deleted row can still be selected.
> deleted row still can be selected out
> -------------------------------------
>
> Key: CASSANDRA-8558
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8558
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: 2.1.2
> java version "1.7.0_55"
> Reporter: zhaoyan
> Fix For: 2.1.3
>
>
> first
> {code}CREATE KEYSPACE space1 WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': 3};
> CREATE TABLE space1.table3(a int, b int, c text,primary key(a,b));
> CREATE KEYSPACE space2 WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': 3};{code}
> second
> {code}CREATE TABLE space2.table1(a int, b int, c int, primary key(a,b));
> CREATE TABLE space2.table2(a int, b int, c int, primary key(a,b));
> INSERT INTO space1.table3(a,b,c) VALUES(1,1,'1');
> drop table space2.table1;
> DELETE FROM space1.table3 where a=1 and b=1;
> drop table space2.table2;
> select * from space1.table3 where a=1 and b=1;{code}
> you will find that the row (a=1 and b=1) in space1.table3 is not deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
