[
https://issues.apache.org/jira/browse/KAFKA-21193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
이선민 updated KAFKA-21193:
------------------------
Description:
SuppressionIntegrationTest takes about 290 seconds locally. 6 of its 14
cases take 42 to 46 seconds each, while the others take about 2 seconds.
Each test method uses a fixed application id, so the withHeaders=false and
withHeaders=true runs share one consumer group. The stream thread does not
leave the group on close, so the second run waits until the previous
member's session times out (45s).
shouldUseDefaultSerdes also reuses the "-shouldInheritSerdes" test id, so
it shares the group and topics with shouldInheritSerdes and its first run
waits as well.
The two shouldShutdownWhen... tests are not affected, because their members
send a LeaveGroup when the stream thread fails.
We can isolate each run with safeUniqueTestName(testInfo), as KAFKA-21133
did for FineGrainedAutoResetIntegrationTest.
JoinStoreIntegrationTest has the same issue: each of its two parameterized
tests reuses an application id across invocations, causing the second
invocation to wait for the previous member's session timeout. Include
both tests in the same fix by giving each invocation a unique application id.
was:
SuppressionIntegrationTest takes about 290 seconds locally. 6 of its 14
cases take 42 to 46 seconds each, while the others take about 2 seconds.
Each test method uses a fixed application id, so the withHeaders=false and
withHeaders=true runs share one consumer group. The stream thread does not
leave the group on close, so the second run waits until the previous
member's session times out (45s).
shouldUseDefaultSerdes also reuses the "-shouldInheritSerdes" test id, so
it shares the group and topics with shouldInheritSerdes and its first run
waits as well.
The two shouldShutdownWhen... tests are not affected, because their members
send a LeaveGroup when the stream thread fails.
We can isolate each run with safeUniqueTestName(testInfo), as KAFKA-21133
did for FineGrainedAutoResetIntegrationTest.
Summary: Speed up SuppressionIntegrationTest and
JoinStoreIntegrationTest (was: Speed up SuppressionIntegrationTest)
> Speed up SuppressionIntegrationTest and JoinStoreIntegrationTest
> ----------------------------------------------------------------
>
> Key: KAFKA-21193
> URL: https://issues.apache.org/jira/browse/KAFKA-21193
> Project: Kafka
> Issue Type: Test
> Components: streams, unit tests
> Reporter: 이선민
> Assignee: 이선민
> Priority: Minor
>
> SuppressionIntegrationTest takes about 290 seconds locally. 6 of its 14
> cases take 42 to 46 seconds each, while the others take about 2 seconds.
> Each test method uses a fixed application id, so the withHeaders=false and
> withHeaders=true runs share one consumer group. The stream thread does not
> leave the group on close, so the second run waits until the previous
> member's session times out (45s).
> shouldUseDefaultSerdes also reuses the "-shouldInheritSerdes" test id, so
> it shares the group and topics with shouldInheritSerdes and its first run
> waits as well.
> The two shouldShutdownWhen... tests are not affected, because their members
> send a LeaveGroup when the stream thread fails.
> We can isolate each run with safeUniqueTestName(testInfo), as KAFKA-21133
> did for FineGrainedAutoResetIntegrationTest.
> JoinStoreIntegrationTest has the same issue: each of its two parameterized
> tests reuses an application id across invocations, causing the second
> invocation to wait for the previous member's session timeout. Include
> both tests in the same fix by giving each invocation a unique application id.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
