kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-6711) GlobalStateManagerImpl should not write offsets of in-memory stores in checkpoint file
Date Wed, 28 Mar 2018 05:56:00 GMT

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

ASF GitHub Bot commented on KAFKA-6711:

cemo opened a new pull request #4782: KAFKA-6711: GlobalStateManagerImpl should not write
offsets of in-mem…
URL: https://github.com/apache/kafka/pull/4782
   This PR is addressing issues when persisting non persistent stores into checkpoint file.

   ### Committer Checklist (excluded from commit message)
   - [x] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> 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
> 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

View raw message