Tag Info

New answers tagged

-1

Maybe use corosync + pacemaker In corosync.conf add the servers, in pacemaker configure virtual IP: primitive FAILOVER-ADDR-CONTROLLER ocf:heartbeat:IPaddr2 \ params ip="z.y.x.w" cidr_netmask="xx" \ op monitor interval="10s" \ meta is-managed="true"


0

Assuming your rabbitmq clients can tolerate a dropped connection, you can consider what's described here. our cluster is behind a VIP. When we want to upgrade a cluster, we spin up an alternate cluster and switch the VIP over to the alternate cluster. Meanwhile, we have tooling that moves messages between clusters. When the 'master' cluster's ...


0

Changing the pool master won't take down the host or any of the VMs. It will cause a restart of the management service (XAPI) of all pool hosts, so that management access via Citrix XenCenter or CLI (xe commands) won't work for 10-30 seconds. Once the service is restarted, you can reconnect to the poolmaster or a slave via XenCenter (you'll be redirected to ...


0

The system is only as strong as the weakest link. In a typical production environment there would be multiples of everything. A small web cluster may consist of a load balancer, several reverse proxies, several http servers, master/slave or master/master database nodes. In this setup the single load balancer would be the weak link; if it dies, nothing ...


2

Basically you want to have an automatic failover for every service needed to run your application. One solution could be the following described aproach: Keepalived installed on both systems. HAProxy as Loadbalancer with failover to HAP LB 2. Monitored by keepalived Apache/NGINX behind HAP. If one failes, HAP will have that monitored and redirects to ...


0

It depends -- for every application and every level of OSI model must be created its own HA system But for start you can learn about ha-proxy, keepalived and nginx with backend


0

It looks like the problem is resolved. Both VMs had idendical MAC-Adresses for there network interfaces. Changed that, rebooted, works.


1

I have tested your configuration on my machine and it worked. Keepalived assigned the VIP to the specified interface and the logs showed the line Keepalived_vrrp: VRRP_Instance(VI_1) Entering MASTER STATE The only way I was able to reproduce your case is by supplying an empty configuration file (the test on non-existent file failed because the startup ...


0

I have rolled out a hybrid IPVS/HAProxy setup. HAProxy was used to do some fairly heavy L7 decision-making, which made it necessary to scale it out at relatively low traffic volumes. Putting IPVS in front gave the ability to do scale-out of the HAProxy nodes, as well as remove the need to manage failover at that layer. It worked fine, for the specific ...


1

Here is the general rule of thumb I have used when deciding between keepalived and heartbeat. Heartbeat is usually used when you want a true active/standby cluster setup (where only one node is actually "up.") Think NFS. Usually w/ Heartbeat the pre and post script actions are used to start and stop services. Keepalived is much simpler, and is usually ...


0

Option 1 is possible with additional servers, but I wouldn't consider using DFS for it. More likely is to use a DAS array / SAN or even some replication to make your application files accessible from both machines. You would then load balance the front end, with a load balancer that itself should be protected from failure by using redundant components or ...


0

We are transferring the DNS entries for the sites that need to be fault tolerant over to DNSMadeEasy. They support failover for DNS entries where they will ping a primary IP and update the A records to a backup IP if the primary is unavailable. They'll switch back when the primary comes back on line.


0

The resolution to the issue where my Availability Group would stay offline when shutting down one of the SQL Services on a node. I had no idea why this was happening as it was once working. I will just say it was human error. What I needed to do: - Administrative Tools --> Failover Cluster Manager - --> Services and applications --> --> Other Resources ...


0

Well obviously you didn't bother to read the manual, because the option to do so is fairly obvious: backup When "backup" is present on a server line, the server is only used in load balancing when all other non-backup servers are unavailable. Requests coming with a persistence cookie referencing the server will always be served though. By ...



Top 50 recent answers are included