Re: where is nextCommitOffset stored?

org.apache.storm storm-kafka-client 2.1.0 On Tue, Jul 21, 2020 at 10:38 PM Rui Abreu wrote: > Old Kafka consumers stored the commit offset in Zookeeper. Which version > are you using? > > On Tue, 21 Jul 2020 at 10:54, Rajat Gangwar > wrote: > >> Hi, >> >>

where is nextCommitOffset stored?

Hi, I am seeing following error in Storm logs: java.lang.IllegalStateException: The offset [2] is below the current *nextCommitOffset* [*5270353*] for [replication-0]. This should not be possible, and likely indicates a bug in the spout's acking I need to know where is the current nextCommitOffs

Re: how to consume/reset aggregated bucket

continue aggregating the same bucket. - After 1 hour repeat the same process. How can I achieve this in Storm ??? any input would help me a lot. Thanks, Rajat On Tue, Mar 28, 2017 at 12:45 PM, Rajat Gangwar wrote: > Use-Case : > > Every hour 100K invoices (entities) are created which a

how to consume/reset aggregated bucket

Use-Case : Every hour 100K invoices (entities) are created which are pushed to Storm. These invoices belong to 'n' users. So Storm does group aggregation on users, and creates aggregated buckets per user. Along with sum of invoices, bucket also contains invoices IDs, so that we know what all invo

Trident Transactional State

Hi, I just started working on Storm, so please forgive if my question is too trivial. :D This doc clearly explain the intricacies needed for achieving exactly-once semantics. But then at the end it says *"The nice thing about Trident is