HailDB Cursor not resetting this->cursor to clustered index after secondary index operations (causing sysbench failure)

Bug #655805 reported by Lee Bieber
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
Undecided
Unassigned
7.0
Fix Released
High
Stewart Smith

Bug Description

Initial symptom was Sysbench failing with HailDB.

http://hudson.drizzle.org/view/Drizzle-staging/job/drizzle-staging-sysbench-readonly-01-haildb/
http://hudson.drizzle.org/view/Drizzle-staging/job/drizzle-staging-sysbench-readwrite-02-haildb/

Investigation showed that we weren't resetting the cursor we track in the HailDBCursor object (to help avoid lots of malloc/free cycles we keep a cursor around) back to the clustered index after an operation on a secondary index (e.g. index scan). This mean we were attempting the UPDATE on the wrong index, ending up with a DB_ERROR from ib_cursor_update_row(), which translates to -1 (hence "error -1 from engine").

Revision history for this message
Stewart Smith (stewart) wrote :

all branches needed for htis should now be in trunk.

Changed in drizzle:
status: New → Fix Released
Revision history for this message
Lee Bieber (kalebral-deactivatedaccount) wrote :
Changed in drizzle:
status: Fix Released → In Progress
Revision history for this message
Stewart Smith (stewart) wrote :

I now know the cause of this, working on a fix

summary: - Get HailDB working with sysbench
+ HailDB Cursor not resetting this->cursor to clustered index after
+ secondary index operations (causing sysbench failure)
description: updated
Revision history for this message
Stewart Smith (stewart) wrote :

There is another bug that I'm tracking before rw sysbench is working 100%, but shouldn't be too long.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.