[
https://issues.apache.org/jira/browse/KAFKA-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295340#comment-13295340
]
Neha Narkhede commented on KAFKA-364:
-------------------------------------
Throwing a +1 on "Allow the consumer to reset its offset to some arbitrary
value, and then write that offset into ZK".
We're currently running into a scenario where we would like to have 100%
reliability, and we're losing a few messages when a connection is broken, but
there were still a few messages in the OS TCP buffers. So, we're planning on
shifting the ZK offset by a few seconds "back in time" if we detect a broker
has gone down, to make sure all the messages will be actually delivered to the
end consumer when that broker comes back up, even if there's a small amount of
overlapping messages.
Thanks,
Marcos
> Consumer re-design
> ------------------
>
> Key: KAFKA-364
> URL: https://issues.apache.org/jira/browse/KAFKA-364
> Project: Kafka
> Issue Type: New Feature
> Reporter: Neha Narkhede
> Assignee: Neha Narkhede
>
> We've received quite a lot of feedback on the consumer side features over the
> past few months. Some of them are improvements to the current consumer design
> and some are simply new feature/API requests. I have attempted to write up
> the requirements that I've heard on this wiki -
> https://cwiki.apache.org/confluence/display/KAFKA/Consumer+Client+Re-Design
> This would involve some significant changes to the consumer APIs, so we would
> like to collect feedback on the proposal from our community. Since the list
> of changes is not small, we would like to understand if some features are
> preferred over others, and more importantly, if some features are not
> required at all.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
