[
https://issues.apache.org/jira/browse/KAFKA-12935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17361367#comment-17361367
]
A. Sophie Blee-Goldman commented on KAFKA-12935:
------------------------------------------------
Hm, actually, I guess that could be considered a bug in itself, or at least a
flaw in the recycling feature – for persistent stores with ALOS, dropping out
of the group only causes tasks to be closed dirty, it doesn't force them to be
wiped out to restore from the changelog from scratch. But with in-memory
stores, simply closing them is akin to physically wiping out the state
directory for that task. Avoiding that was the basis for this recycling feature
in the first place.
This does kind of suck, but at least it should be a relatively rare event. I'm
a bit worried about how much complexity it would introduce to the code to fix
this "bug", but I'll at least file a ticket for it now and we can go from there
> Flaky Test
> RestoreIntegrationTest.shouldRecycleStateFromStandbyTaskPromotedToActiveTaskAndNotRestore
> ----------------------------------------------------------------------------------------------------
>
> Key: KAFKA-12935
> URL: https://issues.apache.org/jira/browse/KAFKA-12935
> Project: Kafka
> Issue Type: Test
> Components: streams, unit tests
> Reporter: Matthias J. Sax
> Priority: Critical
> Labels: flaky-test
>
> {quote}java.lang.AssertionError: Expected: <0L> but: was <5005L> at
> org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) at
> org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6) at
> org.apache.kafka.streams.integration.RestoreIntegrationTest.shouldRecycleStateFromStandbyTaskPromotedToActiveTaskAndNotRestore(RestoreIntegrationTest.java:374)
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
