Bug #50226 Logfile names in ndb_apply_status and ndb_binlog_index stored as latin1?
Submitted: 11 Jan 2010 11:19 Modified: 18 Jan 2010 12:40
Reporter: Hartmut Holzgraefe Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Cluster: Replication Severity:S3 (Non-critical)
Version:* OS:Any
Assigned to: CPU Architecture:Any

[11 Jan 2010 11:19] Hartmut Holzgraefe 
Description:
The ndb_apply_status and ndb_binlog_index tables are created with charset latin1, the binlog file may be on a utf-8 based file system though.

So using either binary or the content of character_set_filesystem may be a better choice to store log file names.

How to repeat:
Check SHOW CREATE mysql.ndb_apply_status

Suggested fix:
Use either either binary or the content of character_set_filesystem when creating those tables
[11 Jan 2010 11:22] Hartmut Holzgraefe 
D4 - might cause issues if master and slave use different file system encoding?
W4 - don't use non-ASCII characters in binlog basename
I5 - haven't seen anyone using non-ascii basenames, and the default setting is using the host name which can't contain non-ascii characters anyway
[15 Jan 2010 9:45] Bernd Ocklin 
Jon, can you document this and then set back to verified? Thanks.
[18 Jan 2010 12:40] Jon Stephens 
Documented in Cluster Limitations section of 5.1 Manual, see here: http://lists.mysql.com/commits/97251

Set back to Verfied per comment from BOcklin.
[17 Mar 2010 0:25] Jon Stephens 
Removed myself as assignee, needs further handling by developers.
[25 Oct 2023 16:52] Magnus Blåudd 
Posted by developer:
 
Both ndb_binlog_index and ndb_apply_status are still using latin1 for the columns that store the log file name. The values written to these columns are written as "array of bytes" so apart from maybe being hard to SELECT it should have no functional limitation to replication as such.