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

Implement optional "long poll" support in fetch request

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • None
    • None

    Description

      Currently, the fetch request is non-blocking. If there is nothing on the broker for the consumer to retrieve, the broker simply returns an empty set to the consumer. This can be inefficient, if you want to ensure low-latency because you keep polling over and over. We should make a blocking version of the fetch request so that the fetch request is not returned until the broker has at least one message for the fetcher or some timeout passes.

      Attachments

        1. KAFKA-48-v4.patch
          62 kB
          Jay Kreps
        2. kafka-48-v3-to-v4-changes.diff
          8 kB
          Jay Kreps
        3. KAFKA-48-v3.patch
          61 kB
          Jay Kreps
        4. KAFKA-48-v2.patch
          46 kB
          Jay Kreps
        5. KAFKA-48.patch
          30 kB
          Jay Kreps

        Issue Links

          blocks

          New Feature - A new feature of the product, which has yet to be developed. KAFKA-50 kafka intra-cluster replication support

          • Major - Major loss of function.
          • Resolved
          is blocked by

          New Feature - A new feature of the product, which has yet to be developed. KAFKA-202 Make the request processing in kafka asynchonous

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              jkreps Jay Kreps
              junrao Jun Rao
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: