Lifecycle

Hydrolix provides a Lifecycle mechanism for ageing out data from the system. The system has two settings one for how long data is made viewable and then how long partitions are kept.

πŸ‘

Age: Configure it!

To configure the age services for your platform information can be found here - Age service

ComponentDescriptionScale to 0
Intake-MiscA deployed server running a number of micro-services. The Decay microservice evaluates partitions for their age and where the partition is older than a set period of time, the partition is made inactive. Once inactive the partition is then evaluated on if it should be deleted (based on another time based setting). Any partitions to be deleted are sent to a queue where the Reaper microservice will then remove the partition from the storage bucket and catalog.Yes
QueuesTwo queues are operated, a listing queue for a list of partitions to be deleted and a dead-letter queue, where jobs are expired to after a period of time if they are not completed.No
HDX DB Storage BucketContains the database (including partitions), configuration and other state information concerning the platform. Forms part of the core infrastructure.No
CatalogContains metadata on the database, partitions and job tasks. Forms part of the core infrastructure.No

Did this page help you?