[MDEV-4003] Cassandra: Error 1032 (Can't find record) on concurrent delete from the same storage through different tables Created: 2013-01-06 Updated: 2014-04-16 Resolved: 2014-04-16 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 10.0.1 |
| Fix Version/s: | 10.0.11 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Elena Stepanova | Assignee: | Sergei Petrunia |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | cassandra | ||
| Issue Links: |
|
||||||||
| Description |
|
Two connections run DELETE from different Cassandra tables which point at the same column family. One DELETE ends with error 1032 "Can't find record".
ORDER BY in the DELETE seems to be important. Run the test below with repeat, e.g.
|
| Comments |
| Comment by Sergei Petrunia [ 2013-01-10 ] |
|
DELETE works by first finding records to delete, and then deleting them. If ORDER BY is present, it may also sort records before doing deletes. It seems, the following happens: connection1 finds a record Maybe, Cassandra SE should ignore the error in this case. |