Bug #20142 show engine ndb status may falsely return latest epoch == 0
Submitted: 30 May 2006 9:56 Modified: 1 Jun 2006 12:44
Reporter: Tomas Ulin Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:5.1.10 OS:
Assigned to: Tomas Ulin CPU Architecture:Any

[30 May 2006 9:56] Tomas Ulin 
Description:
show engine ndb status may falsely return latest epoch == 0

as "latest epoch" is used to sync the binlog this may cause some unexpected behaviour for the user

How to repeat:
e.g.

create table t1 (a int key, b int) engine = ndb;
insert into t1 values (1,1);
update t1 set b=1 where a=1;
show engine ndb status;
[30 May 2006 21:26] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/7058
[1 Jun 2006 5:04] Tomas Ulin 
fixed in 5.1.12
[1 Jun 2006 12:44] Jon Stephens 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented bugfix in 5.1.12 changelog. Closed.