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

expose different data to fetch requests from the follower replicas and consumer clients

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.8.0
    • Fix Version/s: 0.8.0
    • Component/s: core
    • Labels:

      Description

      Currently, the broker always uses highwatermark to calculate the available bytes to a fetch request, no matter where the request is from. Instead, we should use highwatermark for requests coming from real consumer clients and use logendoffset for requests coming from follower replicas.

        Attachments

        1. KAFKA-376-DRAFT.patch
          18 kB
          Prashanth Menon
        2. KAFKA-376-v1.patch
          17 kB
          Prashanth Menon
        3. KAFKA-376-v2.patch
          33 kB
          Prashanth Menon
        4. KAFKA-376-v3.patch
          19 kB
          Prashanth Menon
        5. KAFKA-376-v4.patch
          18 kB
          Prashanth Menon
        6. KAFKA-376-v5.patch
          18 kB
          Prashanth Menon
        7. KAFKA-376-v6.patch
          18 kB
          Prashanth Menon
        8. KAFKA-376-v7.patch
          19 kB
          Prashanth Menon

          Activity

            People

            • Assignee:
              prashanth.menon Prashanth Menon
              Reporter:
              junrao Jun Rao
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 168h
                168h
                Remaining:
                Remaining Estimate - 168h
                168h
                Logged:
                Time Spent - Not Specified
                Not Specified