Controlling Quarantine Data

Controlling Quarantine Data

Watch the video

Quarantined data is comprised of data that has either erred multiple times during attempts to forward it, or could not be stored because of some configuration issues. It is removed from the forward queue to allow other data to pass. The most common reason for data quarantining is an invalid schema in the database for the data that is being stored.

Quarantined data is held indefinitely until the issue is resolved. You can decide to either delete it or re-insert it into the Store and Forward system.

Handling Quarantined Data

1. From the Platform section of the Gateway Webpage, go to System > Store & Forward.

2. Click the three dots menu and select View Details on the Store and Forward engine you would like to see the quarantine data for. The Details panel displays all quarantined data according to the order they were quarantined.

   

3. Each set of data has the option to retry it, delete it, or export it for later use. Choosing export will prompt Ignition to download the quarantined files as JSON. If there are a lot of quarantined records, it may be a good idea to export and delete them so that the Store and Forward engine will not fill up and drop records.

   

   tip

   You can select multiple kinds of quarantine data at the same time by ticking the checkboxes next to each of the items. This will allow you to retry, delete, or export all the selected data at once.

   

4. Fix the problem or error you found that caused the quarantine data.

5. Click on the three dots menu and select Retry, or if the data had been exported, import the data using the Import Quarantine File option.

   

Disk Cache Management

On the Gateway's Platform > System > Store & Forward page, there are two options regarding a database connection's disk cache:

• Archive Disk Cache
• Load Disk Cache

Archive Disk Cache

Attempting to archive a disk cache will result in a confirmation window, stating that the existing cache will be locked and incoming data may be blocked or lost.

During the archiving process:

1. The disk cache is shut down.

2. Archived data is moved to a folder located at %IgnitionInstallationDirectory%/data/var/ignition/store-forward/.archives, making it available to load onto another existing disk cache.

   note

   The cache folder will use the following naming convention: {database name}_{timestamp}.

3. The disk cache is started again, and a new cache folder is created.

Load Disk Cache

Changed in 8.3.10

The Load Disk Cache option has been moved from an engine's three dots menu to a shared location above the Engines list on the right-hand side of the Store & Forward Engines page. Additionally, loading an archived cache now creates a dedicated database connection and data sinks.

Clicking Load Disk Cache opens a popup to select the cache to load. Once selected and loaded, the archived data will be forwarded through a new, duplicated connection based on the original database connection. Duplicated connections from archived disk caches will inlcude an _archive_backfill suffix.

Note that this new connection will also be listed on the Connections > Databases > Connections page. This is where the connection will need to be deleted from when data is done forwarding and is no longer needed.