Cache replication


 

+

Search Tips   |   Advanced Search

 

With replication, data is generated one time and copied or replicated to other servers in the cluster.

Cache replication generates data one time and copies it to other servers in the cluster. Cache entries that are not needed are removed or replaced.

The data replication configuration can exist...

With the cachespec.xml file, we can configure cache replication at the Web container level, but disable it for a specific cache entry.

Cache replication can take on three forms:

PUSH Send out new entries, both ID and data, and updates to those entries.
PULL Requests data from other servers in the cluster when that data is not locally present. This mode of replication is not recommended.
PUSH/PULL Sends out IDs for new entries, then, only requests from other servers in the cluster entries for IDs previously broadcast. The dynamic cache always sends out cache entry invalidations.

We can also perform a batch update. Specifically, for PUSH or PUSH/PULL, the dynamic cache broadcasts the update asynchronously, based on a timed interval rather than sending them immediately when they are created. Invalidations are sent immediately. Distribution of invalidations prevents stale data from residing in a cluster.

See...

In PUSH/PULL mode, the cached object is kept locally on the server that creates it; however, other servers also use the cache ID and store it in the DRSPushPullTable table. If a remote server needs the object, it requests the object by cache ID, or name, from the creating server. Each cache instance has one DRSPushPullTable table that is associated with it.

The following conditions cause the DRSPushPullTable table to grow too big:

Use the following suggestions to resolve the issue:





 

Related tasks

Set cache replication