Bug #68467 CHANGE MASTER TO: should be MASTER_AUTO_POSITION = {0|1}
Submitted: 22 Feb 2013 21:56 Modified: 25 Feb 2013 11:40
Reporter: Santosh Praneeth Banda Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:mysql 5.6.10 OS:Any
Assigned to: Jon Stephens CPU Architecture:Any
Tags: GTID

[22 Feb 2013 21:56] Santosh Praneeth Banda
Description:
When the command CHANGE MASTER TO MASTER_LOG_FILE='', MASTER_LOG_POS='' is executed, it fails with an error 

  ERROR 1776 (HY000): Parameters MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when MASTER_AUTO_POSITION is active.

Mysql 5.6.10 documentation say that
"Currently, MASTER_AUTO_POSITION does not accept any value other than 1. To revert to the older file-based replication protocol, you can issue a new CHANGE MASTER TO statement that specifies at least one of MASTER_LOG_FILE or MASTER_LOG_POSITION. This statement should not include any MASTER_AUTO_POSITION clause, as discussed previously"

But even though MASTER_AUTO_POSITION is not specified in CHANGE MASTER, it's fetching the previous MASTER_AUTO_POSITION value.

How to repeat:
STOP SLAVE; and run CHANGE MASTER TO MASTER_LOG_FILE='', MASTER_LOG_POS=''; on a slave which was running gtid-based replication protocol.

Suggested fix:
Overwrite the stored value of MASTER_AUTO_POSITION when CHANGE MASTER TO is executed.
[23 Feb 2013 13:27] Sveta Smirnova
Thank you for the report.

Verified as described.

Text you mentioned is at http://dev.mysql.com/doc/refman/5.6/en/change-master-to.html

Test case for MTR:

--source include/have_gtid.inc
--source include/master-slave.inc

connection slave;
--vertical_results
show slave status;
stop slave;
CHANGE MASTER TO master_auto_position=1;
CHANGE MASTER TO MASTER_LOG_FILE='foobar', MASTER_LOG_POS=123; 
show slave status;

Option files:

--gtid-mode=on --enforce-gtid-consistency --log-slave-updates --log-bin
[25 Feb 2013 11:40] Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.
[25 Feb 2013 11:41] Jon Stephens
Corrected synopsis.

Fixed in mysqldoc rev 34433.

Closed.