You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "A. Sophie Blee-Goldman (Jira)" <ji...@apache.org> on 2024/04/03 22:11:00 UTC

[jira] [Commented] (KAFKA-12506) Expand AdjustStreamThreadCountTest

    [ https://issues.apache.org/jira/browse/KAFKA-12506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17833758#comment-17833758 ] 

A. Sophie Blee-Goldman commented on KAFKA-12506:
------------------------------------------------

[~goyarpit] yes, it seems this ticket has been abandoned. Feel free to pick it up (and let me know if you have any questions)

 

[~kebab-mai-haddi] if you still want to work on this, just let me know, I'm sure there are multiple improvements that could be made here in parallel

> Expand AdjustStreamThreadCountTest
> ----------------------------------
>
>                 Key: KAFKA-12506
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12506
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: streams, unit tests
>            Reporter: A. Sophie Blee-Goldman
>            Assignee: Arpit Goyal
>            Priority: Major
>              Labels: newbie, newbie++
>
> Right now the AdjustStreamThreadCountTest runs a minimal topology that just consumes a single input topic, and doesn't produce any data to this topic. Some of the complex concurrency bugs that we've found only showed up when we had some actual data to process and a stateful topology: [KAFKA-12503|https://issues.apache.org/jira/browse/KAFKA-12503] KAFKA-12500
> See the umbrella ticket for the list of improvements we need to make this a more effective integration test



--
This message was sent by Atlassian Jira
(v8.20.10#820010)