Suppose we have a simple topology with a spout and a single bolt, and the
tuple timeout is set to some value. When a message exceeds the processing
time allotted, even if the bolt is still working, what happens to that
computation? Does the framework kill the bolt or interrupt the executing
thread
I have a test that starts the topology in local dev mode; the topology
comes up in a separate thread (I don't have to manage that - control is
returned to me as soon as I submit the topology). My test then polls until
it sees the expected results, with a timeout in case something goes wrong.
There'
Does anyone know why the storm command-line program in the bin directory of
the downloads is the storm python script rather than the shell script
that's found in the storm github repo?
We have a minor problem with this script because it explicitly invokes
/usr/bin/python, which is not standard pyt
rmation.
>
> https://storm.apache.org/documentation/Concepts.html
>
> Jake
>
>
>
> On May 12, 2015, at 2:03 PM, Mark Tomko wrote:
>
> When implementing a spout, is it expected that different threads may be
> calling nextTuple() and ack()? That is, if ack() needs to
When implementing a spout, is it expected that different threads may be
calling nextTuple() and ack()? That is, if ack() needs to clean up some
local state, does that state have to be held in a synchronized data
structure?
It seems like that would be necessary, but I've read (somewhere, having
tro
Agreed. If you're using MAX_SPOUT_PENDING, it's better to emit 0 or 1
tuples and let Storm call for the next tuple when it is ready. Probably
best to to 'flatten' your streams upstream of nextTuple so that it can
simple pull one unit of work off the queue and emit it.
On Tue, May 12, 2015 at 3:46
Also, if you have configured a value for "max spout pending" that's larger
than the number of bolts downstream, tuples may wait between when they are
emitted by the spout and when they are processed.
Mark
On Tue, May 12, 2015 at 11:44 AM, Supun Kamburugamuva
wrote:
> Are you running this in a c
t set up correctly?
> If no consumer "subscribes" to a spout (or bolt) the "transfer-count"
> will always be zero.
>
>
> -Matthias
>
> On 05/06/2015 04:51 AM, Mark Tomko wrote:
> > I'm seeing emits to the metrics stream and no others. It's as if the
&g
go all the way to the bottom and click
> on “Show System Stats”. Maybe the numbers will begin to make sense.
>
> Also, you can visualize the stream using the “Show Visualization” button.
>
> From: Mark Tomko
> Reply-To: "user@storm.apache.org"
> Date: 2015,Tuesday,
Hi,
I have a topology that we're working on that seems to have a very long
start-up time, even after the bolts log that they have been prepared.
Looking at the Storm UI, I see tuples that have been "Emitted" but not
"Transferred". The transferred count is 0 for all components, and the
topology has
Regards.
> Jungtaek Lim (HeartSaVioR)
>
> 2015-04-16 1:08 GMT+09:00 Mark Tomko :
>
>> Hi,
>>
>> I'm working on some tests for one of my Storm topologies, and I'm
>> consistently seeing topology timeouts from the testing framework, and it
Hi,
I'm working on some tests for one of my Storm topologies, and I'm
consistently seeing topology timeouts from the testing framework, and it
looks like it's only waiting 5 seconds, which is pretty aggressive in my
opinion:
Error in cluster
java.lang.AssertionError: Test timed out (5000ms)
at ba
Your discovery seems to have helped me, too. I'm not sure yet exactly what
my problem was, but adding the chill-storm dependency and registering the
BlizzardKryoFactory seems to have made it work. Now to go back and see if
there's anything in my configuration that I added in desperation that's no
13 matches
Mail list logo
