mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-27 01:04:19 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mariadb/mysql-test/suite/rpl/r/rpl_show_slave_hosts.result

17 lines
437 B
Text
Raw Normal View History

Merged BUG#49978 from 5.1-bugteam to 5.5-bugteam.
2010-12-19 18:15:12 +01:00
include/master-slave.inc
[connection master]
Bug#13963 SHOW SLAVE HOSTS is unreliable Before the patch, slaves only appear in the output of SHOW SLAVE HOSTS when report-host option is set. If an expected slave does not appear in the list, nobody knows whether the slave does not connect or has started without the "report-host" option. The output also contains a strange field "Rpl_recovery_rank" which has never been implemented and the manual of MySQL5.4 declares that the field has been removed from MySQL5.4. This patch is done with these, According to the manual of MySQL5.4, "Rpl_recovery_rank" is removed. Slaves will register themselves to master no matter if report_host option is set or not. When slaves are registering themselves, their Server_ids, report_host and other information are together sent to master. Sever_ids are never null and is unique in one replication group. Slaves always can be identified with different Server_ids no matter if report_host exists.
2009-10-20 14:30:15 +08:00
RESET SLAVE;
BUG #13963 Postfix
2009-10-23 10:19:50 +08:00
CHANGE MASTER TO master_host='127.0.0.1',master_port=MASTER_PORT,master_user='root';
Bug#13963 SHOW SLAVE HOSTS is unreliable Before the patch, slaves only appear in the output of SHOW SLAVE HOSTS when report-host option is set. If an expected slave does not appear in the list, nobody knows whether the slave does not connect or has started without the "report-host" option. The output also contains a strange field "Rpl_recovery_rank" which has never been implemented and the manual of MySQL5.4 declares that the field has been removed from MySQL5.4. This patch is done with these, According to the manual of MySQL5.4, "Rpl_recovery_rank" is removed. Slaves will register themselves to master no matter if report_host option is set or not. When slaves are registering themselves, their Server_ids, report_host and other information are together sent to master. Sever_ids are never null and is unique in one replication group. Slaves always can be identified with different Server_ids no matter if report_host exists.
2009-10-20 14:30:15 +08:00
START SLAVE IO_THREAD;
Merged BUG#49978 from 5.1-bugteam to 5.5-bugteam.
2010-12-19 18:15:12 +01:00
include/wait_for_slave_io_to_start.inc
Bug#13963 SHOW SLAVE HOSTS is unreliable Before the patch, slaves only appear in the output of SHOW SLAVE HOSTS when report-host option is set. If an expected slave does not appear in the list, nobody knows whether the slave does not connect or has started without the "report-host" option. The output also contains a strange field "Rpl_recovery_rank" which has never been implemented and the manual of MySQL5.4 declares that the field has been removed from MySQL5.4. This patch is done with these, According to the manual of MySQL5.4, "Rpl_recovery_rank" is removed. Slaves will register themselves to master no matter if report_host option is set or not. When slaves are registering themselves, their Server_ids, report_host and other information are together sent to master. Sever_ids are never null and is unique in one replication group. Slaves always can be identified with different Server_ids no matter if report_host exists.
2009-10-20 14:30:15 +08:00
SHOW SLAVE HOSTS;
Server_id Host Port Master_id
BUG #13963 Postfix
2009-10-23 10:19:50 +08:00
3 slave2 DEFAULT_PORT 1
2 SLAVE_PORT 1
Bug#13963 SHOW SLAVE HOSTS is unreliable Before the patch, slaves only appear in the output of SHOW SLAVE HOSTS when report-host option is set. If an expected slave does not appear in the list, nobody knows whether the slave does not connect or has started without the "report-host" option. The output also contains a strange field "Rpl_recovery_rank" which has never been implemented and the manual of MySQL5.4 declares that the field has been removed from MySQL5.4. This patch is done with these, According to the manual of MySQL5.4, "Rpl_recovery_rank" is removed. Slaves will register themselves to master no matter if report_host option is set or not. When slaves are registering themselves, their Server_ids, report_host and other information are together sent to master. Sever_ids are never null and is unique in one replication group. Slaves always can be identified with different Server_ids no matter if report_host exists.
2009-10-20 14:30:15 +08:00
STOP SLAVE IO_THREAD;
Merged BUG#49978 from 5.1-bugteam to 5.5-bugteam.
2010-12-19 18:15:12 +01:00
include/wait_for_slave_io_to_stop.inc
Bug#13963 SHOW SLAVE HOSTS is unreliable Before the patch, slaves only appear in the output of SHOW SLAVE HOSTS when report-host option is set. If an expected slave does not appear in the list, nobody knows whether the slave does not connect or has started without the "report-host" option. The output also contains a strange field "Rpl_recovery_rank" which has never been implemented and the manual of MySQL5.4 declares that the field has been removed from MySQL5.4. This patch is done with these, According to the manual of MySQL5.4, "Rpl_recovery_rank" is removed. Slaves will register themselves to master no matter if report_host option is set or not. When slaves are registering themselves, their Server_ids, report_host and other information are together sent to master. Sever_ids are never null and is unique in one replication group. Slaves always can be identified with different Server_ids no matter if report_host exists.
2009-10-20 14:30:15 +08:00
SHOW SLAVE HOSTS;
Server_id Host Port Master_id
BUG #13963 Postfix
2009-10-23 10:19:50 +08:00
2 SLAVE_PORT 1
Merged BUG#49978 from 5.1-bugteam to 5.5-bugteam.
2010-12-19 18:15:12 +01:00
include/rpl_end.inc
Reference in a new issue Copy permalink