Context Store Geo redundancy overview

Last Updated : Sep 14, 2020 |
Prolog information
Metadata
Keywords:
Context Store Geo redundancy is an architecture that you can configure to enhance high availability of Context Store. Using Context Store Geo redundancy, you can have two Context Store clusters in active/active mode. These Context Store clusters can be either in the same data center or in two different data centers. To ensure a successful failover, you must add the two Context Store clusters to the same System Manager.
Context Store supports Geo redundancy with two Data centers only.
To enable Context Store Geo redundancy, you must:
  • Configure the Context Store Geo attributes: For more information, see Geo redundancy and External Data Mart deployment.
  • Use a load balancer: You must provide and configure a highly available load balancer for the two Context Store clusters. The load balancer must provide:
    • A common address: Both the Context Store clusters must be reachable through a common address. For the third party applications that you integrate with Context Store, use this common address to access the clusters. You must use only the common address, and not the individual cluster address, to access the Context Store clusters.
    • Load balancing: The load can be distributed between the clusters as per your requirements, however, the traffic must be routed on the rid parameter, the routingId field of a context object. You cannot route requests using round robin, least busy server, or any other mechanism other than routing on the rid parameter.
For routing the requests and distributing the traffic between the clusters, Context Store uses an optional field, the rid parameter, in each REST request. If you do not specify a value for the rid parameter, the load balancer routes the request to the default Context Store cluster. Due to the replication of the same context entry in the two clusters, Context Store uses a combination of the rid parameter and the contextId to uniquely identify a context entry.
The two geographically redundant Context Store clusters support the same traffic as one non geo redundant Context Store cluster supports.
Avaya Engagement Designer does not support the geo redundancy feature or the rid parameter of Context Store.
For more information about load balancer for a geo-redundant deployment and a reference configuration, see Avaya Context Store Snap-in Developer Guide.