Controlling Quarantine Data

Controlling Quarantine Data

Watch the video

Quarantined data is data that has erred-out multiple times during attempts to forward it or data that 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, then you can either delete it or re-insert it into the queue.

Handle the Quarantined Data

1. From Status section of the Gateway, go to Connections > Store and Forward.

2. Click the Details tab next to a Store and Forward engine that you would like to see the quarantine data for. Here you will see any quarantined data which are listed according to the order they got quarantined. Each set of data has the option to retry it, delete it, or export it for later use. 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 won't fill up and drop records.

3. Fix the problem/error you found that caused the quarantine data.

4. Click on retry, or if the data had been exported, import the data using the import tool and then retry. This way, you can ensure no data gets lost.

   

Disk Cache Management

New in 8.1.21

In the Gateway's Config > Databases > Store and Forward section, there are two options regarding a database connection's disk cache. Note that the following options will only appear if the Disk Cache Enabled property for the specified database connection is set to true:

• Archive Disk Cache
• Load Disk Cache

Archive Disk Cache

Attempting to archive a disk cache will result in Ignition throwing a warning, saying 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/datacache/archives, making it available to load to replace an existing disk cache. 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

Attempting to load a disk cache will result in Ignition throwing a warning, saying that the existing disk cache will be overwritten.

During the loading process:

1. The local disk cache is stopped and deleted.
2. The chosen archived disk cache is renamed.
3. The disk cache is started again.