Timeline for MySQL replication to slave having VPN connection to Master
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:42 | history | edited | CommunityBot |
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
|
|
| Apr 13, 2017 at 12:13 | history | edited | CommunityBot |
replaced http://serverfault.com/ with https://serverfault.com/
|
|
| Feb 17, 2012 at 15:43 | comment | added | RolandoMySQLDBA |
@Vinny DTest is correct. CHANGE MASTER TO resets relay logs on the Slave only. It does not touch anything on the Master other than what the Slave IO Thread reads.
|
|
| Feb 17, 2012 at 14:26 | comment | added | Derek Downey |
@Vinny If I understand your question right, running CHANGE MASTER TO on a third slave will not affect the other two slaves.
|
|
| Feb 17, 2012 at 13:13 | history | edited | RolandoMySQLDBA | CC BY-SA 3.0 |
added 446 characters in body
|
| Feb 15, 2012 at 18:22 | comment | added | vinny |
Thanks a lot for such an explanatory answer. I really appreciate that. But there is a problem. I already have two slaves replicating from master and if I add this slave, it will be the third. If I execute Change Master to command will it not affect the other two slaves which are on the same network as master and replicating correctly?
|
|
| Feb 15, 2012 at 17:03 | history | edited | RolandoMySQLDBA | CC BY-SA 3.0 |
added 1275 characters in body
|
| Feb 15, 2012 at 16:51 | history | answered | RolandoMySQLDBA | CC BY-SA 3.0 |