I had suggested this, but didn't think it would be the case (I mean... is the box ever wrong?).
Another possible option, should we adjust the uuid() function in how it is doing the generation?
Cheers,
-Brian
On Apr 29, 2010, at 3:40 PM, Eric Day wrote:
> Turns out uuid_generate_time() on this machine is producing duplicate
> UUIDs, which is really bad. I reproduced this behavior outside of
> drizzle as well with:
>
> http://oddments.org/wiki/index.php?id=programming:c:uuid_dupes.c
>
> So, in order to guarantee uniqueness we either need to come up with a
> new uuid function of our own or somehow serialize uuid_generate. A
> simple mutex may not work since CPU clocks may not always be in sync
> with each other. We would probably need to keep a small time history of
> recent UUIDs to provide a guarantee.
>
> --
> drizzleslap guid test fails
> https://bugs.launchpad.net/bugs/568095
> You received this bug notification because you are a member of Drizzle-
> developers, which is subscribed to Drizzle.
>
> Status in A Lightweight SQL Database for Cloud and Web: Confirmed
> Status in Drizzle cherry series: Confirmed
>
> Bug description:
> As of build 1475, the guid test has failed 5 of 7 times
>
> See the complete log at http://hudson.drizzle.org/view/Drizzle-staging/job/drizzle-staging-drizzleslap/193/
>
> Wed Apr 21 12:36:19 2010 INFO: Running test: guid with /home/drizzle/repos/staging-drizzleslap-drizzleslap-r1502/client/drizzleslap --port=9306 --label=guid --concurrency=50 --iterations=10 --csv=/tmp/drizzleslap-1502.csv --number-int-cols=2 --number-char-cols=3 --auto-generate-sql --auto-generate-sql-guid-primary --auto-generate-sql-load-type=write --number-of-queries=100000 --engine=innodb
> Wed Apr 21 12:39:55 2010 INFO: guid Failed with 256
> /home/drizzle/repos/staging-drizzleslap-drizzleslap-r1502/client/drizzleslap: Cannot run query INSERT INTO t1 VALUES (uuid(),601509202,1905068689,'5dfQWSPWlOQP0HHO5AMpvHa22L9mBXR806QNRrtC7BT7KmYQxm7k3hmxvojyBB649YRcFChFOAMkxu2mZ9Wcj9Qex9c8KaCWyXy5kfK0ijcfTXH2gfXFoxtlyLmBvq','ZtMXzy3Jql2QGOxZQW4plteXWds8oozLZDkOBfktOeJY29xLf22GvhnHAYQyCPBlWnAhRmQjGlGJm5YH7aQu7DCHdW7pvARPyTyHFOsX10ig66x5hF0oT4yya5oLG7','e6cSFjk76d8pHEn7BSMB9j77iZ4MuKLOIxsZYcheEhJXn7WyRt2SS9bAbYOTklm3aeS6F1dLiokLvFKF0MjSNBXyjnKJZ6M7kr6rkj4RNpoBw0QwM1Ge4fcfRwzsuL') ERROR : Duplicate entry 'a959aff6-4d7d-11df-8dbf-000e0c434fcf' for key 'PRIMARY'
>
>
Hi!
I had suggested this, but didn't think it would be the case (I mean... is the box ever wrong?).
Another possible option, should we adjust the uuid() function in how it is doing the generation?
Cheers,
-Brian
On Apr 29, 2010, at 3:40 PM, Eric Day wrote:
> Turns out uuid_generate_ time() on this machine is producing duplicate oddments. org/wiki/ index.php? id=programming: c:uuid_ dupes.c /bugs.launchpad .net/bugs/ 568095 hudson. drizzle. org/view/ Drizzle- staging/ job/drizzle- staging- drizzleslap/ 193/ repos/staging- drizzleslap- drizzleslap- r1502/client/ drizzleslap --port=9306 --label=guid --concurrency=50 --iterations=10 --csv=/ tmp/drizzleslap -1502.csv --number-int-cols=2 --number- char-cols= 3 --auto-generate-sql --auto- generate- sql-guid- primary --auto- generate- sql-load- type=write --number- of-queries= 100000 --engine=innodb repos/staging- drizzleslap- drizzleslap- r1502/client/ drizzleslap: Cannot run query INSERT INTO t1 VALUES (uuid() ,601509202, 1905068689, '5dfQWSPWlOQP0H HO5AMpvHa22L9mB XR806QNRrtC7BT7 KmYQxm7k3hmxvoj yBB649YRcFChFOA Mkxu2mZ9Wcj9Qex 9c8KaCWyXy5kfK0 ijcfTXH2gfXFoxt lyLmBvq' ,'ZtMXzy3Jql2QG OxZQW4plteXWds8 oozLZDkOBfktOeJ Y29xLf22GvhnHAY QyCPBlWnAhRmQjG lGJm5YH7aQu7DCH dW7pvARPyTyHFOs X10ig66x5hF0oT4 yya5oLG7' ,'e6cSFjk76d8pH En7BSMB9j77iZ4M uKLOIxsZYcheEhJ Xn7WyRt2SS9bAbY OTklm3aeS6F1dLi okLvFKF0MjSNBXy jnKJZ6M7kr6rkj4 RNpoBw0QwM1Ge4f cfRwzsuL' ) ERROR : Duplicate entry 'a959aff6- 4d7d-11df- 8dbf-000e0c434f cf' for key 'PRIMARY'
> UUIDs, which is really bad. I reproduced this behavior outside of
> drizzle as well with:
>
> http://
>
> So, in order to guarantee uniqueness we either need to come up with a
> new uuid function of our own or somehow serialize uuid_generate. A
> simple mutex may not work since CPU clocks may not always be in sync
> with each other. We would probably need to keep a small time history of
> recent UUIDs to provide a guarantee.
>
> --
> drizzleslap guid test fails
> https:/
> You received this bug notification because you are a member of Drizzle-
> developers, which is subscribed to Drizzle.
>
> Status in A Lightweight SQL Database for Cloud and Web: Confirmed
> Status in Drizzle cherry series: Confirmed
>
> Bug description:
> As of build 1475, the guid test has failed 5 of 7 times
>
> See the complete log at http://
>
> Wed Apr 21 12:36:19 2010 INFO: Running test: guid with /home/drizzle/
> Wed Apr 21 12:39:55 2010 INFO: guid Failed with 256
> /home/drizzle/
>
>