On 2011-11-14 20:44, Marek Marczykowski wrote: > On 14.11.2011 09:55, Raoul Bhatia [IPAX] wrote: >> On 2011-11-11 09:22, Junko IKEDA wrote: >>> Hi, >>> >>> I am running MySQL replication setting with 2 nodes Master/Slave >>> configuration. >>> If Slave status(secs_behind) is lager than Master's >>> parameter(max_slave_lag), >>> Slave data is outdated, right? >>> check_slave() in mysql RA would run "crm_master -v 0" in this >>> situation to mark Slave as "outdated", >>> but if Master is shut down in this status, >>> Slave will be able to promote instead of its old data. >>> (is this correct?) >>> It seems that "crm_master -v -INFINITY" is effectual to prevent Slave >>> promotion. >> >> forwarding this to marek and fghaas as i'm not familiar with >> multi-state handling inside resource agents. > > Did you set "evict_outdated_slaves"?
In a master/slave set, evict_outdated_slaves will actually kick out (by failing with $OCF_ERR_INSTALLED) any slave that has fallen behind. If set to false (the default), then the slave will be allowed to stay in the cluster, but its master preference will be pushed down so it's not promoted, and this seems to be Ikeda-san's preferred behavior. The caveat which I mentioned in my other email in this thread applies here, though. For those pulling this thread from the archives: this information is in the resource agent man page, and in "crm ra info ocf:heartbeat:mysql". Cheers, Florian -- Need help with High Availability? http://www.hastexo.com/now _______________________________________________________ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
