drizzleslap where condition not random

Bug #667200 reported by Andrew Hutchings
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Won't Fix
Critical
Andrew Hutchings
7.0
Won't Fix
Critical
Andrew Hutchings

Bug Description

drizzleslap WHERE condition is not random.

bin/drizzleslap --only-print --label=update-commit --concurrency=50 --iterations=10 --number-int-cols=2 --number-char-cols=3 --auto-generate-sql --auto-generate-sql-add-autoincrement --auto-generate-sql-load-type=update --number-of-queries=100000 --auto-generate-sql-write-number=50000 --commit=8 --engine=innodb > out.sq

grep 796c4422-1d94-102a-9d6d-00e0812d out.sql | wc -l
1000000

796c4422-1d94-102a-9d6d-00e0812d is as every where condition in this case it seems

Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

This only affects --only-print and BLACKHOLE engine.

This is a flaw in the way mysqlslap (and therefore drizzleslap) is designed. By default it uses NULL or uuid() drizzle function to insert and does this on multiple threads and then a select on the pkey to fill the pkey list.

To fix this INSERT generation needs to be completely re-written to generate uuids in code and in a different place so that there are no duplicates.

This will require an OO re-write of drizzleslap. Which may be something for another time. For now Won't Fix.

Changed in drizzle:
status: Triaged → Won't Fix
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.