"The main feature of the 3.0 release is a new decoupled architecture. This change fixes a key limitation found in earlier versions. In earlier versions of Mimir, the ingester component handled both reading and writing. This setup meant that heavy query loads could hurt ingestion performance. The new design adds Apache Kafka as an asynchronous buffer between ingestion and query tasks. This allows each path to scale on its own and removes the cross-path dependencies that affected system stability before."
"This architectural shift brings in "ingest storage," a key element from Grafana Labs. It helps prevent spikes in query volume from slowing data ingestion and vice versa. Internal tests showed big gains in reliability. The risk of read path outages from random ingester failures decreased significantly, especially during the early failure stages. Alongside the architectural overhaul, Mimir 3.0 makes the Mimir Query Engine (MQE) the default query engine."
Grafana Mimir 3.0 introduces a decoupled read/write architecture that isolates ingestion and query workloads. Apache Kafka is used as an asynchronous buffer between ingestion and query tasks so each path can scale independently and avoid cross-path interference. The release includes Grafana Labs' ingest storage to prevent query spikes from slowing ingestion. Internal tests show reduced read-path outages from ingester failures and improved reliability. Mimir Query Engine (MQE) becomes the default, replacing bulk sample processing with a streaming approach that loads only necessary samples and reduces unpredictable memory usage. The project targets extreme scale, aiming to support one billion active series and more.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]