Skip to content

Overview

Overview⚓︎

Resource pools let you dedicate compute and storage resources to specific workloads in Hydrolix. They isolate ingest, merge, or query traffic so you can:

  • Reserve capacity for priority users or dashboards
  • Run heavy ingest pipelines without starving queries
  • Scale services independently instead of over-provisioning one pool

Pools define CPU, memory, storage, and replica counts for a group of pods. You can create pools manually, through the UI or API, or let Hydrolix create them automatically when you configure sources.

Supported services⚓︎

The following services support pools:

  • Intake: intake-head
  • Kafka: kafka-peer
  • Kinesis: kinesis-peer, kinesis-kcl-peer
  • SIEM: akamai-siem-peer
  • Merge: merge-peer
  • Query: query-peer

Resource pool guides⚓︎