Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-3266

Loki - Zone-Aware Replication



    • Epic
    • Resolution: Done-Errata
    • Critical
    • Logging 5.8.0
    • None
    • Log Storage, Loki
    • None
    • Loki - Zone-Aware Replication
    • 13
    • False
    • None
    • False
    • Green
    • NEW
    • Done
    • OBSDA-312 - EFK ES cluster node distribution on multiple zones
    • NEW
    • 100
    • 100% 100%
    • With this update, you can manage zone-aware data replication as an administrator in LokiStack, in order to enhance reliability in the event of a zone failure.
    • Feature



      • Use available pod placement primitives (i.e.Pod Topology Spread Constraints) to spread Loki component pods across availability zones.
      • Ingest logs across replicas in different availability zones.
      • Spread query capabilities across availability zones.


      • Enable creating/modifying custom topologies via the LokiStack API


      As described in previous RFE-1215 requests, our customers run the OpenShift Logging stack on clusters that span multiple availability zones. Historically the OpenShift Logging storage services have not leveraged such pod placement configurations with the result that the entire stack was failing to store logs in case of an availability zone failure. Given the fact that our new stack based on LokiStack has built-in support for zone-aware data replication, we want to expose this capabilities to OpenShift Logging as simple as possible.


      The only alternative is to one log storage (e.g. LokiStack) per availability zone. This has couple of implications that might not be acceptable per case:

      1. The resource requirements for running a LokiStack per zone doubles.
      2. It is required manual intervention as of today to flip the collectors between the available lokistacks per availability zone.

      Acceptance Criteria

      • The data replication of all LokiStack sizes ensures to spread log ingestion for all tenants across availability zones.
      • The query capabilities are partially ensured even in the likely event of an single availability zone failure/

      Risk and Assumptions

      • [RISK] Running the memberlist ring across zones for our setup is something that adds latency to ring operations. This is something we need to benchmark to the bone.
      • [RISK] Running queries and index-gateways across availability means that we have an uniform distribution e.g. 1x.medium declare 3 queries which means 1 in zone a and 2 in zone b and for each zone a single index-gateway replica. This means in case of a zone failure, we loose HA on the other zone too, as 1/2 queries with one index-gateway is left over. We might need to expand the LokiStack sizes in case a user enables zone-aware-replication to ensure that on a zone failure we are still maintaining HA inside the available zone.

      Documentation Considerations

      • Need a good introduction on how users using Pod Topology Spread Constraints can apply their cluster configuration to our API.
      • We do not indent to give API users to define per Loki component pod template topology spread constraints. We want to limit this to the minimum viable set of options. Leaving general configuration to the cluster administrator.

      Open Questions

      1. Does the ingester fail hard when data replication across zones fails?
      2. Does the querier make use of the zone-awareness of the ingesters when querying recent data from them?

      Additional Notes


        Issue Links



              ptsiraki@redhat.com Periklis Tsirakidis
              ptsiraki@redhat.com Periklis Tsirakidis
              Anping Li Anping Li
              Libby Anderson Libby Anderson
              0 Vote for this issue
              7 Start watching this issue