Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-3826

Sampling on throughput / latency metrics recording in Streams

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: streams

      Description

      In Kafka Streams we record throughput / latency metrics on EACH processing record, causing a lot of recording overhead. Instead, we should consider statistically sampling messages flowing through to measures latency and throughput.

      This is based on our observations from KAFKA-3769 and KAFKA-3811.

        Attachments

          Issue Links

          Is contained by

          Bug - A problem which impairs or prevents the functions of the product. KAFKA-5152 Kafka Streams keeps restoring state after shutdown is initiated during startup

          • Blocker - Blocks development and/or testing work, production could not run
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. KAFKA-3769 KStream job spending 60% of time writing metrics

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. KAFKA-3811 Introduce Kafka Streams metrics recording levels

          • Major - Major loss of function.
          • Resolved

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                guozhang Guozhang Wang
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: