[
https://issues.apache.org/jira/browse/KAFKA-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933673#comment-14933673
]
Jay Kreps commented on KAFKA-2592:
----------------------------------
That is generally true for all output, though, right? Not more true with the
k/v data than any other write. I think the fix for that is the txn work, no? In
general we can't delay the write to kafka until the commit point because the
user will in some cases need to control the commit point and we can't buffer
indefinitely.
> Stop Writing the Change-log in store.put() / delete() for Non-transactional
> Store
> ---------------------------------------------------------------------------------
>
> Key: KAFKA-2592
> URL: https://issues.apache.org/jira/browse/KAFKA-2592
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Guozhang Wang
> Assignee: Yasuhiro Matsuda
> Fix For: 0.9.0.0
>
>
> Today we keep a dirty threshold and try to send to change-log in store.put()
> / delete() when the threshold has been exceeded. Doing this will largely
> increase the likelihood of inconsistent state upon unclean shutdown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
