MySQL Bugs: #26783: replication status unknown after cluster or mysqld failure

Bug #26783	replication status unknown after cluster or mysqld failure
Submitted:	2 Mar 2007 4:28	Modified:	11 Jun 2007 21:25
Reporter:	Tomas Ulin	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Replication	Severity:	S4 (Feature request)
Version:	5.1	OS:	Any
Assigned to:	Tomas Ulin	CPU Architecture:	Any

Description:
If replication

innodb/myisam  ->  cluster

and slave cluster or mysqld goes down, the exact state of what has been applied is unknown

How to repeat:
.

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/21404

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/21685

ChangeSet@1.2412, 2007-03-10 18:43:15-08:00, igor@olga.mysql.com +3 -0
  Fixed bug #26783: incomplete string values in a result set column 
  when the column is to be read from a derived table column which 
  was specified as a concatenation of string literals.
  The bug happened because the Item_string::append did not adjust the
  value of Item_string::max_length. As a result of it the temporary 
  table column  defined to store the concatenation of literals was 
  not wide enough to hold the whole value.

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/23613

ChangeSet@1.2538, 2007-04-03 07:20:55+02:00, tomas@whalegate.ndb.mysql.com +8 -0
  Bug #26783 replication status unknown after cluster or mysqld failure
  - update the ndb_apply_status table with binlog info

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/23627

ChangeSet@1.2541, 2007-04-03 09:53:15+02:00, tomas@whalegate.ndb.mysql.com +1 -0
  Bug #26783 replication status unknown after cluster or mysqld failure
  - correction, wrong datatype used

test

Attachment: rpl_ndb_stm_innodb.test (application/octet-stream, text), 4.07 KiB.

reject

Attachment: rpl_ndb_stm_innodb.reject (application/octet-stream, text), 7.30 KiB.

slave option file

Attachment: rpl_ndb_stm_innodb-slave.opt (application/octet-stream, text), 36 bytes.

master option file

Attachment: rpl_ndb_stm_innodb-master.opt (application/octet-stream, text), 41 bytes.

Updated test

Attachment: rpl_ndb_stm_innodb.test (application/octet-stream, text), 5.37 KiB.

Updated Reject

Attachment: rpl_ndb_stm_innodb.reject (application/octet-stream, text), 10.71 KiB.

Except for the end_pos as we discussed, it looks okay to me.
/Jeb

PS: Updated files attached

Pushed into 5.1.18-beta

This has not been pushed to 5.1.18

The changes to ndb_apply_status have been pushed:

mysql> select version();
+-------------------+
| version()         |
+-------------------+
| 5.1.18-beta-debug |
+-------------------+
1 row in set (0.00 sec)

mysql> show create table mysql.ndb_apply_status\G
*************************** 1. row ***************************
       Table: ndb_apply_status
Create Table: CREATE TABLE `ndb_apply_status` (
  `server_id` int(10) unsigned NOT NULL,
  `epoch` bigint(20) unsigned NOT NULL,
  `log_name` varchar(255) CHARACTER SET latin1 COLLATE latin1_bin NOT NULL,
  `start_pos` bigint(20) unsigned NOT NULL,
  `end_pos` bigint(20) unsigned NOT NULL,
  PRIMARY KEY (`server_id`) USING HASH
) ENGINE=ndbcluster DEFAULT CHARSET=latin1
1 row in set (0.01 sec)

This has been documented per Bug #27936 and IRC discussion with Tomas.

The new signature for ndb_apply_status has been pushed.  Values in it are not updated yet.

BR,

Tomas

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/27544

ChangeSet@1.2520, 2007-05-29 11:55:12+02:00, tomas@whalegate.ndb.mysql.com +2 -0
  Bug #26783  	replication status unknown after cluster or mysqld failure

Pushed into 5.1.20-beta

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 bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Documented bugfix in 5.1.20 changelog.

Also documented for telco-6.2.3 release.