Problems with cluster's virtual IP -


I apply 99% high altitude cluster using heartbeat / korosinic + pacemaker for communication between some servers. I am planning to do this but these machines are not in the same gateway / netmask and I can not share a virtual IP for heart beat. There is a way to fix it without plug-in all servers in the same router (because its not the option) ???

Thanks for the attention

Availability of 99% means that your system Makes more tolerance Downtime for one to three and a half days a day, you should be able to achieve that availability with commodity hardware and without using pacemaker.

If you want the possibility of high availability or system maintenance, you can get high uptime using DNS without interrupting the service. You can either manually switch DNS records of TTL or use a service such as an Amazon Route 53 to switch automatically if any kind of health check fails. You can.

Comments

Popular posts from this blog

java - ImportError: No module named py4j.java_gateway -

python - Receiving "KeyError" after decoding json result from url -

.net - Creating a new Queue Manager and Queue in Websphere MQ (using C#) -