Hi Kotipalli,
You would always point your MySQL slaves to the same master server – you don’t
want your second slave to receive “second hand news”. Also – if you pointed
slave 2 to slave 1 and the synchronization to slave 1 died for some reason (not
uncommon) then you would end up with two slaves out of date.
Hope this makes sense.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
dag.sonst...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
On 06/02/2017, 12:44, "kotipalli venkatesh" <venkateshcloudt...@gmail.com>
wrote:
Hi Sergey,
As suggested, we created a cloud database and then imported the dump
without any warning/error message.
Thanks for sharing knowledge.
Hi All,
I have another doubt, currently environment having HA of Database servers
(Master+Slave) both the servers working fine.
a. we deployed 3rd DB server and point to the 1st DB Master server as a
slave server is a good method ?
or
b. 3DB server pointed to 2 DB Slave server so in this scenario 2DB server
again master of 3 DB server.
Can anyone please suggest me best method.
Regards,
Venkatesh.k
On Sat, Feb 4, 2017 at 12:04 PM, Sergey Levitskiy <
sergey.levits...@autodesk.com> wrote:
> You pretty much OK with the mysqldump options you use. ACS doesn't use
> MySQL events or triggers so you should be good with all-databases flag.
