Embedded Ignite Cache

GGSA implements an Embedded Ignite Cache. Ignite can be used as a target or a reference for any pipeline, to persist events. In case of GoldenGate, the pipeline persists incoming events containing full record, and also updates the cache with modified events, making available the latest modified records.

Note:

Ignite Caching is not supported in the GGSA marketplace instance.

Starting a Cache Cluster

To start an Embedded Cache Cluster:

1. Open System Settings and click the Cache Cluster tab.
2. Update the Persistence Store Path to a preferred accessible location. This path will be the persistence storage for cached data. Default is set as /tmp/ignite/persistence.

   Note:

   NFS mounted path is the preferred persistence store path, to enable cache rehydration, on restart of a cluster or a node.
3. Click Start Cluster.

Note:

When you start a cache cluster for the first time, an embedded Ignite Connection is created with connection type as Ignite Cache and Connection Name as Embedded. This connection is not editable connection, and connection details are not shown, but you can select this connection while creating an Ignite Target and an Ignite Reference.

Stopping a Cache Cluster

To stop a running Embedded Cache Cluster:

1. Open System Settings and click the Cache Cluster tab.

   The Cluster Status shows previous valid status, by default. The status is updated with the current status from server. You will see a green icon, indicating a running server status.

   Persistence Store Path is not editable, if the cluster is in running state.

2. Click Stop Cluster.

On a successful stop action, the cluster status changes to Stopped, and the persistence store path becomes editable.

Restarting a Cache Cluster

To restart a running Embedded Cache Cluster:

1. Open System Settings and click the Cache Cluster tab.

   The Cluster Status shows previous valid status, by default. The status is updated with the current status from server. You will see a red icon, indicating a killed server status.

2. Click Restart Cluster.

On a successful cluster restart, the status changes to Running, and the persistence store path is not editable.

Monitoring Cache in the Cache Cluster

You can monitor the caches in both the internal (embedded) and external clusters, using the Monitor option on the GGSA application's homepage.

To monitor a cache:

1. Click Monitor on the homepage.

2. On the Cache Management screen, select a cache connection from the drop-down list.

   The Cache Management page is populated with the following details for the selected cache connection:

   • All the Cache connections created using ignite, which includes both internal and external caches, are listed. Internal caches created from the System Settings tab are marked Embedded.
   • By default, all the caches created using the first connection in the list are displayed. If you select another connection from drop-down list, the corresponding caches will be retrieved and listed.
   • The Created Target column lists all the targets created using a cache.
   • The Referred By column lists the references created using a cache.
   • Click the Reset Cache icon to clear all the cache entries.
   • Click the Reload Cache icon to reload the cache size.
   • The caches are displayed in the ascending order of their names, by default. Use the Sort By option, to sort the caches by name or size.