Activity log for bug #655805

Date Who What changed Old value New value Message
2010-10-06 15:57:01 Lee Bieber bug added bug
2010-10-06 15:57:13 Lee Bieber nominated for series drizzle/elliott
2010-10-06 15:57:13 Lee Bieber bug task added drizzle/elliott
2010-10-06 15:57:22 Lee Bieber drizzle/elliott: importance Undecided High
2010-10-06 15:57:25 Lee Bieber drizzle/elliott: status New In Progress
2010-10-06 15:57:35 Lee Bieber drizzle/elliott: assignee Stewart Smith (stewart)
2010-10-14 04:09:34 Stewart Smith drizzle: status New Fix Released
2010-10-14 04:09:35 Stewart Smith drizzle/elliott: status In Progress Fix Released
2010-10-14 04:09:58 Stewart Smith drizzle/elliott: milestone 2010-10-25
2010-10-14 16:02:48 Lee Bieber drizzle: status Fix Released In Progress
2010-10-14 16:02:51 Lee Bieber drizzle/elliott: status Fix Released In Progress
2010-10-26 22:26:34 Stewart Smith drizzle/elliott: milestone 2010-10-25 2010-11-08
2010-11-09 20:17:32 Lee Bieber drizzle/elliott: milestone 2010-11-08 2010-11-22
2010-11-23 06:05:25 Stewart Smith drizzle/elliott: milestone 2010-11-22 2010-12-06
2010-12-07 23:16:50 Stewart Smith drizzle/elliott: milestone 2010-12-06 2010-12-20
2010-12-13 04:45:38 Stewart Smith summary Get HailDB working with sysbench HailDB Cursor not resetting this->cursor to clustered index after secondary index operations (causing sysbench failure)
2010-12-13 04:47:57 Stewart Smith description Need to get HailDB working with sysbench 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/ 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").
2010-12-13 12:32:55 Stewart Smith drizzle/elliott: status In Progress Fix Committed
2010-12-13 14:34:35 Launchpad Janitor branch linked lp:~stewart/drizzle/haildb-2.3-baghdad-updates
2010-12-14 22:01:49 Lee Bieber drizzle/elliott: status Fix Committed Fix Released