Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-22026

Handling delta bundle size exceeding Kafka's default message limit

XMLWordPrintable

    • Product / Portfolio Work
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Provide the required acceptance criteria using this template.

      • ...
      Show
      Provide the required acceptance criteria using this template. ...
    • Critical
    • None

      Value Statement

      Ensure the issue title clearly reflects the value of this user story to the
      intended persona. (Explain the "WHY")

      After refactoring the bundle into delta mode, there are still two cases we cannot handle:

      1. Single oversized object: If an individual object exceeds 800 KB, we cannot send the bundle—even if it contains only that one object.

      2. Large metadata size: If the combined metadata of all objects exceeds 800 KB, the message cannot be sent due to Kafka's size limit.

      Possible solutions for handling oversized objects or bundles:

      1. Make Kafka message size configurable: Update the CR limits, client-side settings, and remove hardcoded assertions on bundle size(related pr: https://github.com/stolostron/multicluster-global-hub/pull/1800).

      2. Chunk the message: Split the bundle into smaller chunks to handle edge cases.

       

      Definition of Done for Engineering Story Owner (Checklist)

       

      Development Complete

      • The code is complete.
      • The compliance is synced into the database
      • Any required downstream Docker file changes are made.

      Tests Automated

      • [ ] Unit/function tests have been automated and incorporated into the
        build.
      • [ ] 100% automated unit/function test coverage for new or changed APIs.

      Secure Design

      • [ ] Security has been assessed and incorporated into your threat model.

      Multidisciplinary Teams Readiness

      • [ ] Create an informative documentation issue using the Customer

      Portal Doc template that you can access from [The Playbook](

      https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

      and ensure doc acceptance criteria is met.

      • Call out this sentence as it's own action:
      • [ ] Link the development issue to the doc issue.

      Support Readiness

      • [ ] The must-gather script has been updated.

              rh-ee-myan Meng Yan
              daliu@redhat.com DangPeng Liu
              Hui Chen Hui Chen
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: