Bug #17248 incomplete sync_replication_* options should be removed
Submitted: 8 Feb 2006 23:18 Modified: 27 Apr 2006 13:27
Reporter: Timothy Smith Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:5.0.18 OS:Any (any)
Assigned to: Bugs System CPU Architecture:Any

[8 Feb 2006 23:18] Timothy Smith
An incomplete feature, mis-named synchronized replication, is in the 5.0 server.  There are several user-visible portions of the code.  They look interesting, but should not be used, and are not documented.

How to repeat:


| sync_replication          | 0     |
| sync_replication_slave_id | 0     |
| sync_replication_timeout  | 10    |

mysqld --verbose --help:

                      Enable synchronous replication.
                      Synchronous replication is wished for this slave.
                      Synchronous replication timeout.

Suggested fix:

The user-visible portions of this code should be removed.  The rest of the code should be documented internally as incomplete, until such time as it can be replaced by a robust solution, completed and documented, or removed entirely.
[12 Apr 2006 8:22] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

[12 Apr 2006 8:23] Greg Lehey
Removed all code relating to synchronous replication.  Anything left behind would be too old and mouldy to be of any use.
[27 Apr 2006 13:16] Elliot Murphy
Fixed for 5.0.21, 5.1.10.
[27 Apr 2006 13:27] Paul DuBois
No changelog entry needed. These variables were never
documented because they were unused.
[27 Apr 2006 14:17] Sheeri Cabral
rpl_recovery_rank is another variable that shows up when I do a SHOW STATUS in 4.0.20, 4.1.14 and 5.0.18

mysql> SHOW VARIABLES LIKE "rpl%";
| Variable_name     | Value |
| rpl_recovery_rank | 0     |
1 row in set (0.01 sec)