Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Bryan Irvine (sparctacusgmail.com)
Date: Thu Mar 12 2009 - 13:02:47 CDT
The information is there and the replica can connect on a reboot but
only if that information has not changed correct?
e.g. I reboot the slave, and on the master just run "reset master;"
the bin.000001 could change to bin.000002 and the pos change from 98
to 15443 or some such. If I do that do I then need to re-run the "set
master to" statements when the slave comes back up? or can that be
On Thu, Mar 12, 2009 at 10:26 AM, Rob Wultsch <wultschgmail.com> wrote:
> When you start up replication the data should be recorded in the
> master.info in your data dir.
> [rootsomeserver ~]# cat /var/lib/mysqldata/master.info
> I am not familiar with any setups where the master.info would not be
> created, and I am too lazy too look for a setting that would lead to
> such an silly/annoying state.
> On Thu, Mar 12, 2009 at 10:03 AM, Bryan Irvine <sparctacusgmail.com> wrote:
>> Do I jsut need to monitor better and manually add it should the log
>> and pos change?
>> On Wed, Mar 11, 2009 at 7:05 PM, Baron Schwartz <baronxaprb.com> wrote:
>>> That's deprecated too :-)
>>> On Wed, Mar 11, 2009 at 9:17 PM, Cui Shijun <rancpinegmail.com> wrote:
>>>> #2. try adding the information of master into my.cnf then restart the server.
>> MySQL General Mailing List
>> For list archives: http://lists.mysql.com/mysql
>> To unsubscribe: http://lists.mysql.com/mysql?unsub=wultschgmail.com
> Rob Wultsch
> wultsch (aim)
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql