From: Ananda Kumar Date: August 26 2010 3:22pm Subject: Re: master-slave replication sync problems. List-Archive: http://lists.mysql.com/mysql/222697 Message-Id: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=0016e659f4d85f98b3048ebb929f --0016e659f4d85f98b3048ebb929f Content-Type: text/plain; charset=ISO-8859-1 Smith, I never said, this wont work.Some times, there are chances of lossing data. regards anandkl On Thu, Aug 26, 2010 at 8:48 PM, wrote: > Quoting Norman Khine : > > i see, so the best is to just stop slave and then check the master >> status, and when the master status syncs then i start the slave? >> >> >> >> > Well Im willing to hear from others experiences, but if you really shouldnt > have to do anything. If you want you can issue a stop slave before the > reboot and a start slave after, but it shouldnt make any difference. And Im > not sure what you refer to when you talk about the master status syncing. > The master will continue to increment the binlog when changes are made > regardless of whether the slave is up. If the slave has been rebooted and is > behind the master binlog pos it should automatically sync those changes when > started... > > > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql?unsub=anandkl@stripped > > --0016e659f4d85f98b3048ebb929f--