>1- I am unable to get how it guarantees that "the state saved at A and B
>represents the state that’s the result of all the tuples that arrived from the
>spout before C1" because ordering is not guaranteed while transfer from
>upstream bolt to downstream bolt.
Ordering is preserved
On Tue, Mar 28, 2017 at 1:07 PM, Alexandre Vermeerbergen <
avermeerber...@gmail.com> wrote:
> Hi Harsh,
>
> Thanks a lot for your answer.
>
> So you mean that I should look for kafka spout offsets in the zookeeper
> servers which Storm uses for Nimbus/Supervisors communications, is that
>
Hello Arun,
Thanks for the nice explanation. But I have little doubts:
1- I am unable to get how it guarantees that "*the state saved at A and B
represents the state that’s the result of all the tuples that arrived from
the spout before C1" *because ordering is not guaranteed while transfer
Anyone doing (rolling) upgrades from 1.0.2 to 1.0.3?
Best regards,
Robin Verlangen
*Chief Data Architect*
Disclaimer: The information contained in this message and attachments is
intended solely for the attention and use of the named addressee and may be
confidential. If you are not the
Hi Harsh,
Thanks a lot for your answer.
So you mean that I should look for kafka spout offsets in the zookeeper
servers which Storm uses for Nimbus/Supervisors communications, is that
right ?
My problem is to find the zk path of these offsets: in the zookeeper
servers associated to my Kafka
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
The storm stores its offset in the Zookeeper, it is connected to. So, you
won't find the offset information for the storm clients in the same place
where other clients' offsets are. You must have provided topic id in Spout
Config in Storm, this is where it stores the offset information in its
