MySQL Bugs: #64213: Documentation fails to warn binary loggers of problems with ndbcluster writes

Bug #64213	Documentation fails to warn binary loggers of problems with ndbcluster writes
Submitted:	2 Feb 2012 18:48	Modified:	13 Feb 2012 9:46
Reporter:	Kevin Benton	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.0	OS:	Any (any)
Assigned to:	Jon Stephens	CPU Architecture:	Any

Description:
--ndb-log-update-as-write issues don't show up on the Binary Log page for users that are replicating from MySQL Cluster to a non-MySQL Cluster server. It's hard to troubleshoot these issues if the documentation doesn't warn users early that there is incompatibility in the default configuration when logging from a MySQL Cluster SQL(API) node and a stand-alone MySQL server.

I would like to see some kind of caution to users in this specific set-up of what they need to look out for so others don't run into problems where some of the changes made to data in the cluster don't make it to the stand-alone slave.

How to repeat:
See SR 3-4043823321

Suggested fix:
Add comments to the documentation as described above.

http://dev.mysql.com/doc/refman/5.0/en/binary-log.html
http://dev.mysql.com/doc/refman/5.1/en/binary-log.html
http://dev.mysql.com/doc/refman/5.5/en/binary-log.html
http://dev.mysql.com/doc/refman/5.6/en/binary-log.html

Thank you for the documentation request.

Fixed by mysqldoc r29114.

Closed.