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

Enhance Kafka to allow a leader to be blacklisted if it fails to read/write beyond a configurable baseline

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 0.9.0.0, 0.10.0.0
    • Fix Version/s: None
    • Component/s: replication
    • Labels:
      None
    • Environment:
      RHEL 6.8

      Description

      According to the documentation, for a leader to be considered alive, it must be able to maintain its session with ZooKeeper via ZooKeeper's heartbeat mechanism.

      As this criteria stands, a leader will continue to attempt to fulfill the read/write requests for in-sync replicas without taking into account resource availablity, performance factors, or hardware/application health. This introduces the risk of unchecked degradation to the performance and/or reliability of data read/write operations to a subset of data sources in the event of a server problem, and the risk grows with partition leader density

      A viable solution to this may be some type of logic that allows a leader to be blacklisted as such if it fails to read/write beyond a configurable baseline.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mj034032 Macoy Jones
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: