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

Increase per broker connection limit

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • Increase per broker connection limit to 3000
    • False
    • None
    • False
    • Yes
    • No
    • To Do
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      The connection count limit of OpenShift Streams for Apache Kafka has been increased from 3000 to 9000 for 1 Streaming Unit and from 6000 to 18000 for 2 Streaming Units. This enhancement allows more clients to connect to your OpenShift Streams for Apache Kafka instance.
      Show
      The connection count limit of OpenShift Streams for Apache Kafka has been increased from 3000 to 9000 for 1 Streaming Unit and from 6000 to 18000 for 2 Streaming Units. This enhancement allows more clients to connect to your OpenShift Streams for Apache Kafka instance.
    • Enhancement
    • ---
    • ---
    • MK - Sprint 227

      The current limit of 1000 connections per broker is not sufficient to handle a few customer scenarios, this limit needs to be increased to 3000 per broker or 1SU to 9000.

      The increase in latency is not a big concern when reaching higher connection limits

      A small increase in resource cost could be negotiated in terms of increasing this limit.

      The disparity in broker connection distribution due to the placement of partition leaders is a separate concern, and should not be part of this issue.

      rhn-gps-ddoyle 

              Unassigned Unassigned
              rhn-engineering-rareddy Ramesh Reddy
              Kafka Fleet Services
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: