#Haproxy default port code
If HAProxy receives a status code other than 200, then it would automatically route traffic to the secondary Cloudant instance. As long 200 response code is received, traffic is routed to the primary Cloudant instance. For example, a simple GET request(let’s say in every 5 seconds) sent to this endpoint to see if the “200” response code is returned. So all we have to do is ping this endpoint as a ‘heartbeat at a regular interval of time.
#Haproxy default port how to
How to check if the Cloudant instance is up? 🔗Ĭloudant offers a simple way to know if it is available or not through the _up endpoint. Target architecture with HAProxy as a reverse proxy 🔗ġ) HA Proxy should route traffic to the primary Cloudant instance as long as it is up.Ģ) HA Proxy should automatically route traffic to secondary Cloudant instance if the primary instance goes down.ģ) HA Proxy should automatically route traffic back to the primary Cloudant instance as soon as it is up again. In this article, we will use HAProxy or High Availability Proxy to direct traffic to one of two Cloudant instances(active-passive configuration) with auto failover to the backup Cloudant instance. For more information about setting this up, see Configuring IBM Cloudant for cross-region disaster recovery Active-passive configuration is preferred as in the case of active-active configuration we have to additionally create a strategy for managing conflicts to avoid problems with multiple copies of data. Prerequisite : Set up an active-passive configuration that uses two IBM Cloudant accounts, one in each region. This would be easy, efficient, and save time compared to doing it through application logic. To enable auto-failover, we can put an HTTP proxy server in front of IBM Cloudant and then configure our application to talk to the proxy server rather than the IBM Cloudant instance directly. For either configuration, IBM Cloudant doesn’t provide a facility to manage explicitly any failover or reroute requests between Cloudant regions and has to be implemented within the application logic itself, or by using a load balancer/proxy. The IBM Cloudant helps you build a flexible disaster recovery capability into your applications through a cross-region disaster recovery setup using either active-passive or active-active configuration.
0 kommentar(er)
