You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2019/02/21 06:16:00 UTC
[jira] [Commented] (KAFKA-7967) Kafka Streams: some values in
statestore rollback to old value
[ https://issues.apache.org/jira/browse/KAFKA-7967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773699#comment-16773699 ]
Matthias J. Sax commented on KAFKA-7967:
----------------------------------------
Thanks for reporting this. Can you share your DSL code (without business logic)? Does it affect specific stores in the topology or all stores? Do you have exactly-once enabled? Do you have DEBUG level logging enabled? Can you try to disable caching to see if the issue persists?
> Kafka Streams: some values in statestore rollback to old value
> --------------------------------------------------------------
>
> Key: KAFKA-7967
> URL: https://issues.apache.org/jira/browse/KAFKA-7967
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Ziming Dong
> Priority: Critical
>
> We are using kafka streams 2.1.0, we use both persistentKeyValueStore statestore and persistentWindowStore statestore. We found sometimes both types of statestore could `fetch` old values instead of newly updated values. We didn't find any logs except INFO level logs, no instance restart in the period, also there is no rebalance log which indicates it's not a rebalance bug. The bug happened no more than one time each week, but many records were affected each time, and we didn't find a way to reproduce it manually.
> For example, the issue may happen like this, note the changelog contains all the `update`:
> # got value 1 from key 1
> # update value 2 to key 1
> # got value 2 from key 1
> # update value 3 to key 1
> # got value 1 from key 1(something wrong!!)
> # update value 2 to key 1
> there is only one type log as follow
>
> {code:java}
> 2019-02-19x14:20:00x xxxxxx INFO [org.apache.kafka.clients.FetchSessionHandler] [xxxxxxx-streams-xx-xxx-xxxx-xxx-xxxxxx-StreamThread-1] [Consumer clientId=xxxxxxxxx-xxxx-xxx-xxx-xxxx-xxxxx-StreamThread-1-consumer, groupId=xxxxxxxxx] Node 2 was unable to process the fetch request with (sessionId=1998942517, epoch=4357): INVALID_FETCH_SESSION_EPOCH.
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)