This is most likely an issue with process limits. Check your process limits
in your supervisor nodes with "unlimited -a" and increase to 64k or so if
it's low (e.g. 1k). Even if you aren't creating threads, storm is, and a
lot of other libraries such as database client libraries do too.
On Jun 12,
HI!
For me it seems that the your HBase bolt is loosing the connection with
zookeeper and it tries over and over to connect via thread.
Please check your zookeeper health. Do your HBase cluster and Storm
cluster are using the same Zookeeper? How many Hbase region servers and
how many storm
Hello,
Do you have any solution to make log dir for each topology with just
one logback file cluster.xml on supervisor nodes?
One workaround we used is to manually load logback config in each
component. But this will disable built-in logviewer. And make development
more complicated.
Hi,
Your message says it is throwing OutOfMemory error. So, you should look
into what is causing that. It may not be really because of storm but it may
be because of application code also. You may want to use `
-XX:+HeapDumpOnOutOfMemoryError` and `-XX:HeapDumpPath=/worker/dumps` to
dump heap on
Hi Wenwei
Actually, I did not new any thread in my bolt. The error reported just comes
from storm core itself.
I t seems you created too many threads, that
cause no available thread resource.
Sent from my iPhone
On Jun 12, 2016, at 10:18, "fanxi...@travelsky.com"