MySQL Bugs: #24839: readAutoIncrementValue(): Tuple did not exist

Bug #24839	readAutoIncrementValue(): Tuple did not exist
Submitted:	5 Dec 2006 21:54	Modified:	12 Nov 2009 8:57
Reporter:	Constantinos Giatras	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: NDB API	Severity:	S3 (Non-critical)
Version:	mysql-5.0	OS:	Linux (RHEL4)
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	5.0.32 bitkeeper

Description:
The following error shows up when you do a table status on a NDBCLUSTER engine table with no data:

061205 10:04:43 [ERROR] Error 626 in readAutoIncrementValue(): Tuple did not exist

How to repeat:
show table status `ndb_table_no_data`

can't reproduce

drop table if exists n1;
create table n1(i int primary key auto_increment, j int) engine=ndb;
show table status like "n1";
insert into n1 set j=23;
delete * from n1;
show table status like "n1";
insert into n1 set j=42;
truncate table n1;
show table status like "n1";

no error log entries produced by any of the SHOW statements

I'm sorry I may have left out some relative information. We had a problem with tables in the cluster that did not have an autoincrement key. We followed this post / bug report, and downloaded the 5.0.32 source and patched it with this:

http://bugs.mysql.com/bug.php?id=21033

After that patch and reinstall, the autoincrement bug was not happening, but we then started seeing the bug that I reported.

Hope this helps,

Kosta

please retest on newer version (e.g 6.3.27a or so)

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".