Hey,
I've build a cluster with one pacemaker resource named ClusterIP. The
change by failover is very fast and is ok. My problem is that services
like apache or mysql take at least 10-15 seconds to respond after IP
takeover. Is there a change to fast this up ?
Apache VirtualHost respond an
On 12-01-23 04:59 AM, Niclas Müller wrote:
Hey,
I've build a cluster with one pacemaker resource named ClusterIP. The
change by failover is very fast and is ok. My problem is that services
like apache or mysql take at least 10-15 seconds to respond after IP
takeover. Is there a change to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Heyho,
Am 23.01.2012 09:59, schrieb Niclas Müller:
I've build a cluster with one pacemaker resource named ClusterIP.
The change by failover is very fast and is ok. My problem is that
services like apache or mysql take at least 10-15 seconds to
An Active Active Cluster would be great, but I need always one Virtual
IP or?
To got an Downtime of less 2 seconds would be interested. But this
switch of the Virtual IP from Host to host is needed verytime or?
On 01/23/2012 01:58 PM, Robert Schumann wrote:
-BEGIN PGP SIGNED MESSAGE-
An Active Active Cluster would be great, but I need always one Virtual
IP or?
To got an Downtime of less 2 seconds would be interested. But this
switch of the Virtual IP from Host to host is needed verytime or?
If your services are already running in the background it would be enough just
to
I've tryed something like this already. The IP changed but the running
service react on the Virtual-IP after 10-15 sec. I've wonderd
On 01/23/2012 02:54 PM, Michael Schwartzkopff wrote:
An Active Active Cluster would be great, but I need always one Virtual
IP or?
To got an Downtime of less 2
On 01/23/2012 08:35 AM, Niclas Müller wrote:
I've tryed something like this already. The IP changed but the running
service react on the Virtual-IP after 10-15 sec. I've wonderd
With active/passive it's usually the database that slows things down:
with shutdown transactional it can take