Hi ,
found this capabilities in storm Spout.
https://github.com/nathanmarz/storm-contrib/tree/master/storm-kafka
Another very useful config in the spout is the ability to force the spout
to rewind to a previous offset. You do forceStartOffsetTime on the spout
config, like so:
spoutConfig.forceSt
Kafka allows a consumer to rewind the consumption since messages are kept
in the broker by a retention policy (defaults to 7 days). I am not exactly
sure how Storm works. My guess is that it only checkpoints the consumer
offset after all messages before that offset have been processed
successfully.
I try to resolve such behavior:
suppose storm consumes messages from kafka. In case part of it's
consumers crashed for any reasons and as a result didn't succeed to process
the consumed messages. But if it is impossible after recover to reprocess
these messages the system will not be robust and
As @Milind said, it is possible that a consumer consumes the same message
more than once.
This happens when there is an unclean shutdown of the consumer and it is
not able to commit its latest offset to Zookeeper. When the failed consumer
comes up, it would fetch the stale offset from zookeeper thu
It is possible to consume the same message more than once with the same
consumer. However WHAT you actually do with the message (such as idempotent
writes) is the tricker part.
Regards
Milind
On Wed, Jul 31, 2013 at 8:22 AM, Oleg Ruchovets wrote:
> Hi ,
>
> I just don't know which mail list is
Hi ,
I just don't know which mail list is correct to post this question( storm
or kafka)? Sorry for cross post.
I just read the documentation which describe guaranteed message
processing with storm -
https://github.com/nathanmarz/storm/wiki/Guaranteeing-message-processing.
The question actua
