[
https://issues.apache.org/jira/browse/STORM-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720227#comment-14720227
]
Parth Brahmbhatt commented on STORM-1017:
-----------------------------------------
I am fine with removing the config as long as we document what users will have
to do manually when they want zookeeper offsets to be ignored i.e. what paths
from zookeeper needs to be deleted.
We need to restart the discussion on STORM-650. My personal stand is to forget
about backward compatibility and just re-write kafka spout from scratch. That
code has reached a pretty unmaintainable state IMO and we are adding more and
more features on top of it.
> If ignoreZkOffsets set true,KafkaSpout will reset zk offset when recover from
> failure.
> --------------------------------------------------------------------------------------
>
> Key: STORM-1017
> URL: https://issues.apache.org/jira/browse/STORM-1017
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-kafka
> Reporter: Renkai Ge
> Assignee: Sriharsha Chintalapani
>
> when ignoreZkOffsets set true and startOffsetTime =
> kafka.api.OffsetRequest.EarliestTime().
> workers running -> topology shutdown by user and restart -> workers will read
> from earliest time again
> workers running -> one of workers shutdown by accident and supervisor restart
> the worker -> what offset will the restarted worker read from?
> More details on
> https://github.com/apache/storm/pull/493#issuecomment-135783234
> It will cause a lot of unwanted duplicated messages in some scenes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
