On 07/24/2012 10:23 PM, l...@netcourrier.com wrote:
> I have mysql in master/slave replication on 2 nodes
> (centreon-failover-dbmaster and centreon-failover-dbslave). In normal state,
> role 'master' is on 'centreon-failover-dbmaster' and 'slave' role is on
> 'centreon-failover-dbslave'. The procedure:
> - I halt the server 'centreon-failover-dbmaster' ('halt' command): it's ok.
> The role 'master' is switched on 'centreon-failover-dbslave' and there is no
> issue in replication (i have checked)
> - there is some writes on new MySQL masters
> - I start the server 'centreon-failover-dbmaster': it's not ok. I have a
> MySQL replication issue (duplicate entry key).
Please show us `/var/log/mysqld.log` on the 'centreon-failover-dbmaster'?
> Moreover, i would prefer to avoid an auto failback (master/slave role). When
> the master switches, how can i do to tell me to stay ? (like with the
> stickiness) I don't want a command after to use (because if the server is up
> before the command: database is not synced anymore)
It's already done. When the failed master ('centreon-failover-dbmaster')
comes back on line, it becomes a new slave of 'centreon-failover-dbslave'.
>
> Thanks a lot.
>
> Best regards,
>
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
