[
https://issues.apache.org/jira/browse/STORM-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Nusbaum updated STORM-1954:
--------------------------------
Summary: Large Trident topologies can cause memory issues due to
DefaultResourceDeclarer object reading config (was: Large Trident topologies
can cause memory issues due to Node object reading config)
> 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)
