Recently Viewed Topics
silo – An Elasticsearch index used to store LCE events data; a silo is always part of activeDb.
snapshot – An archived silo; a snapshot is always part of archiveDb.
- Total size of activeDb is limited by config attribute
active-size(default: 20 TB).
- Total size of archiveDb is limited by config attribute
archive-size(default: 20 TB).
Every 3.5 minutes, LCE will:
read in the results of the last-executed action, from
choose the next action to take based on the last-executed action
perform the next action and store results in
Storing the state in this manner has the following advantages:
simplicity (no separate logic to handle reloads/restarts is needed)
transparency (to see exactly where the archival algorithm is, just query
available emergency override (can alter the control flow by updating lce_status.db)Note: This is not standard operating procedure and should only be performed in very rare cases.
LCE waits a maximum of 75 minutes for an archive job to complete in order to avoid being stuck in the
CheckArchiveDone state indefinitely in the rare case that Elasticsearch fails to report an archive job as complete.
See Elasticsearch Administration and Troubleshooting Utilities for descriptions of relevant archiving tools.