Table of Contents

GeoServer push replication quickly and efficiently replicates changes to stored data at a remote ScaleOut StateServer (SOSS) store in order to allow for uninterrupted availability after a site-wide failure.

Push Replication

Push replication replicates the following operations from the local ScaleOut store to one or more remote stores:

  • Creation of new objects.

  • Updates to objects and object metadata.

  • Removal of objects.

  • Refreshes to sliding object timeouts due to read accesses.

The GeoServer option is configured to replicate objects from a local ScaleOut store to a remote ScaleOut store in one direction only. If the GeoServer option is also licensed on a remote SOSS store, it can be separately configured to replicate objects to the local store. For example, to configure GeoServer to replicate objects bi-directionally between sites A and B, it must be configured on site A to replicate objects to site B and then configured on site B to replicate objects to site A.

Note

To avoid circular replication, GeoServer Push replication does not perform cascading data replication (for example, replicating objects from site A to B and then forwarding site A's objects to site C). To replicate objects from site A to sites B and C, configure site A to replicate objects directly to both sites B and C.

Using Push Replication

Push replication is configured and managed using ScaleOut's mangement tools (see the ScaleOut Product Suite's User Guide for more information). Once push replication has been configured, all objects in the local ScaleOut store will be subject to replication by default; every create, update, and delete operation performed will be sent across the WAN connection to the remote datacenter(s) to keep objects the stores synchronized. In addition, refreshes to sliding object timeouts are replicated when objects are retrieved on the local store.

Disabling Push Replication

Application developers can disable replication for individual objects. Use the GeoServerPushPolicy property to specify whether an object should be subject to replication as the object is created.

To disable push replication for an entire cache, use the SetGeoServerPushPolicy(GeoServerPushPolicy) when building the cache to configure the cache's default behavior. If push replication is disabled for an entire cache, it can be re-enabled for individual objects at object creation time using a CreatePolicy.