You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Kyle Nusbaum (JIRA)" <ji...@apache.org> on 2016/07/08 21:20:11 UTC
[jira] [Updated] (STORM-1954) Large Trident topologies can cause
memory issues due to Node object reading config
[ https://issues.apache.org/jira/browse/STORM-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kyle Nusbaum updated STORM-1954:
--------------------------------
Description:
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.
was:
Trident Node 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 Node.
> Large Trident topologies can cause memory issues due to Node 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)