Unsubscribe
Sent from BlueMail
On Aug 9, 2017, 8:40 AM, at 8:40 AM, "Hannum, Daniel"
wrote:
>I think the problem is that capacity of 3.5. That indicates that
>there’s a backlog on that bolt, so it’s saying that actual time spent
>processing in the bolt is
Severity: High
Vendor: The Apache Software Foundation
Versions Affected:
Apache Storm 1.0.0, 1.0.1, 1.0.2, 1.0.3
Apache Storm 1.1.0
Description:
It was found that under some situations and configurations of storm it is
theoretically possible for the owner of a topology to trick the supervisor
" Using direct grouping will let the bolt upstream of the ES writing bolt
decide which ES bolt receives a given message. So you could have spouts ->
sorter bolts -> ES bolts, where sorter bolts use direct grouping to
partition the stream by index id in whatever way you need. "
What is
Hi Bobby,
I am using Storm 1.1.0. Oh, I forgot. F.Y.I, before I turn on the feature,
the section is displayed. However, according to kishorvpatil's
comment(https://issues.apache.org/jira/browse/STORM-1157?jql=text%20~%20%22Worker%20profiling%22)
, it shouldn't. Is this a problem? In
I'm not sure. That should be enough. There might be a bug in the ui code
though. What version of storm are you using? Also did you select any workers
to profile?
- Bobby
On Tuesday, August 8, 2017, 8:53:10 PM CDT, ? ??
wrote:
#yiv8119227291 body