This widget appears on the Store management screen, and lets the user perform operations to purge various sections of DPOD's Big Data Store according to data type, as specified below.
These are sensitive operations, which might affect your system in unexpected ways. These operations cannot be rolled back.
Do not perform these operations if you are unsure how they will affect your system.
The only operational situation where deleting an index set is recommended, is when sensitive data was collected using WS-M agents.
To safely delete this sensitive data, first shut down all WS-M Collectors (using the app-util scripts) and then delete the Index set.
Wait for 1-2 minutes until the index set is recreated before you start the WS-M collectors again.
Operation | Description | Usage |
|---|---|---|
Delete Syslog TRAN Data | Purge transaction records received via Syslog | User |
Delete Syslog SYS ERROR Data | Purge system error records received via Syslog | User |
Delete Syslog AUTH Data | Purge system authorization records received via Syslog | User |
Delete Syslog DEFAULT Data | Purge system default records received via Syslog(unclassified) | User |
Delete WS-M Data | Purge payload information recorded by WS-M | User |
Delete DEVICE Resources Data | Purge device resource information recorded by the Device Resource agent | User |
Delete SERVICE Resources Data | Purge device resource information recorded by the Service Resource agent | User |
Delete Services Configuration Data (ES) | Purge service configuration information recorded by the Service Resource agent | User |
Delete Logical Tran FULL Data | Internal use | SYSTEM Only |
Delete Logical Tran COMPACT Data | Internal use | SYSTEM Only |
Delete IIB Tran Data | Internal use | SYSTEM Only |
Delete Services Configuration Data (DB) | Internal use | SYSTEM Only |
Delete Internal Operations Data | Internal use | SYSTEM Only |
Delete Static Data | Internal use | SYSTEM Only |
For more information on storage locations and capacity, see the index sets descriptions on Store.