Hi Pradeep,
It seems you want to send one tuple from spout to Bolt then bolt will write
it to a file and some other cosumer/bolt will read from file. And while
consumer reading, other tuple can be received by bolt and may write more
content on the same file.
is this right? if yes then continue read
I don't know the "storm signals" project you mentioned. It might work
for you. It is not part of storm-core system.
However, I do not understand why you write to a file and read from it
again. Why not using one more bolt and just process the tuples there?
I would also not sleep the spout in your
Hi,
The problem i have is that, i write the tuples received form a spout to a
file through a bolt. I also use another thread to read form it. Sometime
the writer might overtake reader and override tuple which the reader has to
read and lose tuples. So i have to avoid this..
I heard about two things
No, currently there's no way to leave a message from downstream to
upstream.
Other tricky way is sharing external storage (like ZK) and setting a flag
value manually.
Hope this helps.
Thanks,
Jungtaek Lim (HeartSaVioR)
2015년 6월 29일 월요일, Pradheep s님이 작성한 메시지:
> Hi,
>
> I have a spout which is em
It depends what you want so accomplish... You can always "sleep" in
Spout.nextTuple() to block the spout for a finite time.
As an alternative, you can limit the number of pending tuples be setting
parameter "topology.max.spout.pending" (be aware that tuples might time
out in this case).
Sending a
