You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "John Roesler (Jira)" <ji...@apache.org> on 2020/06/01 20:52:00 UTC

[jira] [Updated] (KAFKA-10068) Verify HighAvailabilityTaskAssignor performance with large clusters and topologies

     [ https://issues.apache.org/jira/browse/KAFKA-10068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Roesler updated KAFKA-10068:
---------------------------------
    Fix Version/s: 2.6.0

> Verify HighAvailabilityTaskAssignor performance with large clusters and topologies
> ----------------------------------------------------------------------------------
>
>                 Key: KAFKA-10068
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10068
>             Project: Kafka
>          Issue Type: Task
>          Components: streams
>    Affects Versions: 2.6.0
>            Reporter: John Roesler
>            Priority: Blocker
>             Fix For: 2.6.0
>
>
> While reviewing [https://github.com/apache/kafka/pull/8668/files,] I realized that we should have a similar test to make sure that the new task assignor completes well within the default assignment deadline. 30 seconds is a good upper bound.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)