Problem: IO thread fails to connect to master if servers are configured with
special character sets like utf16, utf32, ucs2.
Analysis: MySQL server does not support few special character sets like
utf16,utf32 and ucs2 as "client's character set"(eg: utf16,utf32, ucs2).
It is known limitation listed in the documentation
http://dev.mysql.com/doc/refman/5.5/en/charset-connection.html.
The default value for default-character-set parameter is 'auto'
which means that if the server's character set is not supported,
then server automatically changes client's character set to
predefined character-set which is 'latin1' in the current code.
Eg:
$ ./mysql -uroot -S$SOCKET_FILE --default-character-set=utf16
ERROR 1231 (42000): Variable 'character_set_client' can't be set to the value of 'utf16'
$ ./mysql -uroot -S$SOCKET_FILE will be successfully connected to
server with 'latin1' as default client side character set.
When IO thread is trying to connect to Master, it sets server's character
set as client's character set. When Slave server is started with these
special character sets, IO thread (which is like a connection to Master)
fails because of the above said limitation.
Fix: Now even IO thread also behaves the same as a regular client behaves.
i.e., If server's character set is not supported as client's character set,
then set default's client character set(latin1) as client's character set.
2015-01-14 14:13:52 +05:30
|
|
|
################################################################################
|
|
|
|
|
# Bug#19855907 IO THREAD AUTHENTICATION ISSUE WITH SOME CHARACTER SETS
|
|
|
|
|
# Problem: IO thread fails to connect to master if servers are configured with
|
|
|
|
|
# special character sets like utf16, utf32, ucs2.
|
|
|
|
|
#
|
|
|
|
|
# Analysis: MySQL server does not support few special character sets like
|
|
|
|
|
# utf16,utf32 and ucs2 as "client's character set"(eg: utf16,utf32, ucs2).
|
|
|
|
|
# When IO thread is trying to connect to Master, it sets server's character
|
|
|
|
|
# set as client's character set. When Slave server is started with these
|
|
|
|
|
# special character sets, IO thread (a connection to Master) fails because
|
|
|
|
|
# of the above said reason.
|
|
|
|
|
#
|
|
|
|
|
# Fix: If server's character set is not supported as client's character set,
|
|
|
|
|
# then set default's client character set(latin1) as client's character set.
|
|
|
|
|
###############################################################################
|
|
|
|
|
--source include/master-slave.inc
|
2015-05-04 22:00:24 +02:00
|
|
|
call mtr.add_suppression("Cannot use utf16 as character_set_client");
|
Problem: IO thread fails to connect to master if servers are configured with
special character sets like utf16, utf32, ucs2.
Analysis: MySQL server does not support few special character sets like
utf16,utf32 and ucs2 as "client's character set"(eg: utf16,utf32, ucs2).
It is known limitation listed in the documentation
http://dev.mysql.com/doc/refman/5.5/en/charset-connection.html.
The default value for default-character-set parameter is 'auto'
which means that if the server's character set is not supported,
then server automatically changes client's character set to
predefined character-set which is 'latin1' in the current code.
Eg:
$ ./mysql -uroot -S$SOCKET_FILE --default-character-set=utf16
ERROR 1231 (42000): Variable 'character_set_client' can't be set to the value of 'utf16'
$ ./mysql -uroot -S$SOCKET_FILE will be successfully connected to
server with 'latin1' as default client side character set.
When IO thread is trying to connect to Master, it sets server's character
set as client's character set. When Slave server is started with these
special character sets, IO thread (which is like a connection to Master)
fails because of the above said limitation.
Fix: Now even IO thread also behaves the same as a regular client behaves.
i.e., If server's character set is not supported as client's character set,
then set default's client character set(latin1) as client's character set.
2015-01-14 14:13:52 +05:30
|
|
|
CREATE TABLE t1(i VARCHAR(20));
|
|
|
|
|
INSERT INTO t1 VALUES (0xFFFF);
|
|
|
|
|
--sync_slave_with_master
|
|
|
|
|
--let diff_tables=master:t1, slave:t1
|
|
|
|
|
--source include/diff_tables.inc
|
|
|
|
|
# Cleanup
|
|
|
|
|
--connection master
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
--source include/rpl_end.inc
|