[
https://issues.apache.org/jira/browse/KAFKA-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590885#comment-16590885
]
Naveen commented on KAFKA-6711:
-------------------------------
hello there
We have developed a kafka-streams application using Kafka Server and Kafka
Client both version 1.1.0. In 2 of our environment we are seeing this issue
where offsets for GlobalTable (in-memory) stores are written in checkpoint
file. We updated the kafka-client and kafka-streams libraries in our
environment to 1.1.1 whereas the Kafka Server is still on 1.1.0. After deleting
the GlobalTable checkpoint file the streaming application creating the file
again but it still had the offsets written in it.
My question here is will this fix only work if Kafka Server as well as Kafka
Streams Client both are updated to version 1.1.1? Please advise.
Here is the code snippet we use GlobalTable creation.
{code:java}
final GlobalKTable<String, EdgeInfo> edgeInfos =
builder.globalTable(SystemTopic.EDGE_INFO_BY_GUID.defaultSerializer().keySerde(),
SystemTopic.EDGE_INFO_BY_GUID.defaultSerializer().valueSerde(),
SystemTopic.EDGE_INFO_BY_GUID.topicName(),
"store");{code}
thanks
Naveen Gauba
> GlobalStateManagerImpl should not write offsets of in-memory stores in
> checkpoint file
> --------------------------------------------------------------------------------------
>
> Key: KAFKA-6711
> URL: https://issues.apache.org/jira/browse/KAFKA-6711
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 1.0.1
> Reporter: Cemalettin Koç
> Assignee: Cemalettin Koç
> Priority: Major
> Labels: newbie
> Fix For: 0.10.2.2, 0.11.0.3, 1.0.2, 1.1.1, 2.0.0
>
>
> We are using an InMemoryStore along with GlobalKTable and I noticed that
> after each restart I am losing all my data. When I debug it,
> `/tmp/kafka-streams/category-client-1/global/.checkpoint` file contains
> offset for my GlobalKTable topic. I had checked GlobalStateManagerImpl
> implementation and noticed that it is not guarded for cases similar to mine.
> I am fairly new to Kafka land and probably there might be another way to fix
> issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
