[
https://issues.apache.org/jira/browse/STORM-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368509#comment-15368509
]
ASF GitHub Bot commented on STORM-1954:
---------------------------------------
GitHub user knusbaum opened a pull request:
https://github.com/apache/storm/pull/1547
STORM-1954: Large Trident topologies can cause memory issues due to
DefaultResourceDeclarer object reading config
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/knusbaum/incubator-storm STORM-1954
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/1547.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 #1547
----
commit 55c9e1fc7d030a0a381af34ba726cf2d4a19e953
Author: Kyle Nusbaum <[email protected]>
Date: 2016-07-08T21:22:12Z
Fix for STORM-1954
----
> Large Trident topologies can cause memory issues due to
> DefaultResourceDeclarer object reading config
> -----------------------------------------------------------------------------------------------------
>
> Key: STORM-1954
> URL: https://issues.apache.org/jira/browse/STORM-1954
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Kyle Nusbaum
>
> DefaultResourceDeclarer objects each read the full config on instantiation.
> We've seen this causing slow startup and OOMs for large Trident topologies.
> The config should be static in DefaultResourceDeclarer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
