Hi,
We're looking at using msyqlfailover to automatically detect issues with our current master and deal with the subsequent failover operations for us.
One thing I haven't been able to find is a way to run more than one instance of mysqlfailover checking the same master (for redundancy purposes). If I just run one copy and the server it's running on dies I lose my automated failover capabilities until that's detected and fixed, but I can imagine that trying to run two copies at the same time might not end well if both of them decide to fail over at the same time.
Is there any recommended way to deal with this, or should I just try to work around it by implementing my own monitoring/locking mechanism?
Also, does anybody know what the status of the project now that InnoDB cluster is out? Will this get abandoned in favour of the clustering solution or will it continue to be worked on independently?
Thanks!
We're looking at using msyqlfailover to automatically detect issues with our current master and deal with the subsequent failover operations for us.
One thing I haven't been able to find is a way to run more than one instance of mysqlfailover checking the same master (for redundancy purposes). If I just run one copy and the server it's running on dies I lose my automated failover capabilities until that's detected and fixed, but I can imagine that trying to run two copies at the same time might not end well if both of them decide to fail over at the same time.
Is there any recommended way to deal with this, or should I just try to work around it by implementing my own monitoring/locking mechanism?
Also, does anybody know what the status of the project now that InnoDB cluster is out? Will this get abandoned in favour of the clustering solution or will it continue to be worked on independently?
Thanks!