Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.8.0, 0.8.1, 0.8.1.1
    • Fix Version/s: 0.8.3
    • Component/s: replication
    • Labels:

      Description

      Currently, there is no good way to tune the replica lag configs to automatically account for high and low volume topics on the same cluster.
      For the low-volume topic it will take a very long time to detect a lagging
      replica, and for the high-volume topic it will have false-positives.
      One approach to making this easier would be to have the configuration
      be something like replica.lag.max.ms and translate this into a number
      of messages dynamically based on the throughput of the partition.

      1. documentation.diff
        3 kB
        Aditya Auradkar
      2. documentation.diff
        3 kB
        Aditya Auradkar
      3. KAFKA-1546_2015-03-11_18:48:09.patch
        36 kB
        Aditya A Auradkar
      4. KAFKA-1546_2015-03-12_13:42:01.patch
        37 kB
        Aditya A Auradkar
      5. KAFKA-1546_2015-03-16_11:31:39.patch
        54 kB
        Aditya A Auradkar
      6. KAFKA-1546_2015-03-17_14:46:10.patch
        63 kB
        Aditya A Auradkar
      7. KAFKA-1546_2015-03-25_13:27:40.patch
        63 kB
        Aditya A Auradkar
      8. KAFKA-1546_2015-03-26_17:44:08.patch
        79 kB
        Aditya A Auradkar
      9. KAFKA-1546_2015-03-27_11:57:56.patch
        81 kB
        Aditya A Auradkar
      10. KAFKA-1546.patch
        34 kB
        Aditya A Auradkar

        Activity

          People

          • Assignee:
            Aditya Auradkar
            Reporter:
            Neha Narkhede
          • Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development