High consistency and failover

In a high consistency environment, the proxy server does not round robin read operations. Instead, the proxy sever directs all read and write operations for a single partition to a single back-end server.

Sometimes, high consistency is required by applications, for instance, an application may write some data then immediately perform a search to ensure the update was correct. High Consistency is configurable on a per split basis.

To enable high consistency, you need to set the attribute ibm-slapdProxyHighConsistency to true.

Sample Entry
dn: cn=o\=sample split, cn=ProxyDB, cn=Proxy Backends, cn=IBM Directory, 
cn=Schemas, cn=Configuration
cn: o=sample split
ibm-slapdProxyNumPartitions: 1
ibm-slapdProxyPartitionBase: o=sample
ibm-slapdProxySplitName: samplesplit
ibm-slapdEnableAutoFailBack: true
ibm-slapdProxyHighConsistency: true
objectclass: top
objectclass: ibm-slapdConfigEntry
objectclass: ibm-slapdProxyBackendSplitContainer

All read and write operations within a single partition are directed to a single back-end server. When the primary back-end server goes down the proxy will failover to a secondary server that is configured. All read and write operations will then be directed towards that server until the primary server is restored.