kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lucas Bradstreet (Jira)" <j...@apache.org>
Subject [jira] [Created] (KAFKA-8899) Optimize Partition.maybeIncrementLeaderHW
Date Wed, 11 Sep 2019 21:26:00 GMT
Lucas Bradstreet created KAFKA-8899:

             Summary: Optimize Partition.maybeIncrementLeaderHW
                 Key: KAFKA-8899
                 URL: https://issues.apache.org/jira/browse/KAFKA-8899
             Project: Kafka
          Issue Type: Task
          Components: core
    Affects Versions: 2.2.1, 2.3.0
            Reporter: Lucas Bradstreet

Partition.maybeIncrementLeaderHW is in the hot path for ReplicaManager.updateFollowerFetchState.
When replicating between brokers with high partition counts, maybeIncrementLeaderHW becomes
expensive, with much of the time going to calling Partition.remoteReplicas which performs
a toSet conversion. maybeIncrementLeaderHW should avoid generating any intermediate collections
when calculating the new HWM.

This message was sent by Atlassian Jira

View raw message