[
https://issues.apache.org/jira/browse/STORM-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997522#comment-14997522
]
ASF GitHub Bot commented on STORM-1190:
---------------------------------------
GitHub user revans2 opened a pull request:
https://github.com/apache/storm/pull/870
STORM-1190: System Load too high after recent changes
This helps a fair amount at the low end, but not as much as I had hoped.
The spout seems to sleeping more with batching enabled which is offsetting some
of the gains from updating the DisruptorQueue code. I really have not idea why
at this point.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/revans2/incubator-storm STORM-1190
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/870.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #870
----
commit d3d125e9f6bf2500ed027fec7d0aa32e99918a57
Author: Robert (Bobby) Evans <[email protected]>
Date: 2015-11-09T20:43:43Z
STORM-1190: System Load too high after recent changes
----
> System load spikes in recent snapshot
> -------------------------------------
>
> Key: STORM-1190
> URL: https://issues.apache.org/jira/browse/STORM-1190
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
> Affects Versions: 0.11.0
> Environment: 10x (CoreOS stable (766.4.0) / k8s 1.0.1 / docker
> running on Azure VMs)
> Reporter: Michael Schonfeld
> Priority: Critical
> Attachments: Screenshot 2015-11-08 22.17.57.png, Screenshot
> 2015-11-08 22.18.06.png
>
>
> We've been running Storm's snapshots on our production cluster for a little
> while now (that back pressure support really helped us), and we've noticed a
> sudden spike in system load when going from
> commit@ba1250993d10ffc523c9f5464371fbeb406d216f to the current latest
> commit@c12e28c829fcfabc0a3a775fb9714968b7e3e349. Both versions were running
> the exact same topologies, and there was no significant change in workload.
> Not exactly sure how to even begin to debug this, so we ended up just rolling
> back. Thoughts?
> Stats screenshots attached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
