Please verify that logviewer daemon is running or not. To run this use
./storm logviewer &
Sent from my Sony Xperia™ smartphone
I PVP wrote
>body{font-family:Helvetica,Arial;font-size:13px}
>
>What needs to be done to make the host>:8000/daemonlog?file=nimbus.log and :8000/daemonlog
Hello,
I am using Storm 0.10.0 and have an application pulling content off a Kafka
topic via the Kafka spout but after some time nothing is being injected.
However, after a restart of the topic, more messages come in for a while. I
have done my best to confirm that there are no tuple timeouts by
What needs to be done to make the :8000/daemonlog?file=nimbus.log and :8000/daemonlog?file=supervisor.log
to work ?
The Storm UI is running fine on :8080 . But links from within
the UI that are pointing to :8000 are not working.
Running Storm 1.0.1 on RedHat and no firewall is blocking an
Hello, if I wanted to run a bolt able to process 30k concurrent requests on
a single server, how would I go about it? Those requests are asynchronous
requests to remote servers.
Hi Satish, yes the spout is emitting messages. The topology works fine in
the start. Then the failed count on the spout gradually increases and last
3 bolts stop processing after a while but the other bolts still process and
emit.
On Thu, Aug 4, 2016 at 8:11 PM, Satish Duggana
wrote:
> Hi Abhish
Hi Abhishek,
Did you check whether spout is really emitting messages?
On Thu, Aug 4, 2016 at 5:42 PM, Abhishek Raj wrote:
> Thanks for the quick response. According to storm documentation, if a
> worker/node dies it's automatically restarted. Also, the bolts still show
> up in storm ui. They jus
Thanks for the quick response. According to storm documentation, if a
worker/node dies it's automatically restarted. Also, the bolts still show
up in storm ui. They just don't seem to be processing any data. The link
you mentioned could have been of great help but we're stuck on an old
version righ
The last time I encountered crashes that left no error messages, was when
the OS killed a process that took up too much processing power. This gets
worse on Ubuntu systems, where there is no log registered about the OOM
killer even in the system logs.
For debugging Storm, there are these options:
h
Hi.
We are using storm 0.9.4. Our topology consists of a linear chain of 1
spout and 8 bolts. In the 4th bolt we call an external bolt written in php
which emits to 5th bolt after some processing.
We are seeing that after some time, the 6th, 7th and 8th bolt completely
stop processing. The execute
