Uploaded image for project: 'Managed Service - Streams'
  1. Managed Service - Streams
  2. MGDSTRM-9519

Reduce the number of nodes required for the Kafka infra pool

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • Reduce the number of nodes required for the Kafka infra pool
    • False
    • None
    • False
    • No
    • To Do
    • MGDSRVS-52 - Ensure our service is profitable or has a profitability path
    • 0% To Do, 0% In Progress, 100% Done
    • ---
    • ---

      The formula to determine the required number of OpenShift worker nodes to be able to run a given number of RHOSAK Kafka instance is calculated using the following formula: ($DESIRED_KAFKA_UNIT_LIMIT×3) + 12 + 3*ceil(MAX(0, $DESIRED_KAFKA_UNIT_LIMIT - 32)/16) = Number of nodes

      This implies that the "Kafka infra" pool, i.e. all the nodes required on the OSD instance to run RHOSAK service, excluding the actual Kafka instance brokers, is currently 12. This seems excessive. E.g. to run a single 3 broker Kafka instance on an OSD datacplane would currently require 15 (!!!) worker nodes.

      We need to find a way to reduce this base "Kafka infra" pool to reduce the costs of running our service.

              rhn-engineering-rareddy Ramesh Reddy
              rhn-gps-ddoyle Duncan Doyle (Inactive)
              Kafka Fleet Services
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: