[
https://issues.apache.org/jira/browse/STORM-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367670#comment-15367670
]
Robert Joseph Evans commented on STORM-1952:
--------------------------------------------
We do some of that already with the distributed cache, where we have an LRU
cache for these objects. I would prefer for us to follow the same kind of
policy that way we can keep the code around in case we need it, but we can also
delete it if we need space and it has not been "used" in a long time (meaning
no worker that needs it has run on this node for a while).
Otherwise we risk running out of disk space.
> Keeping topology code for supervisor until topology got killed
> --------------------------------------------------------------
>
> Key: STORM-1952
> URL: https://issues.apache.org/jira/browse/STORM-1952
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-core
> Affects Versions: 1.0.0, 2.0.0, 1.0.1
> Reporter: Jungtaek Lim
>
> It's based on review comment from [~sriharsha].
> https://github.com/apache/storm/pull/1528/files#r69152524
> Please feel free to change reporter if you would like to.
> In supervisor we're removing topology code when assignments for that
> supervisor has gone.
> But there's valid scenario to need to keep the topology code though
> assignments for that supervisor is none, for example, rebalancing.
> So it would be better for supervisor to keep topology code until topology has
> been killed (and all topology workers assigned to that supervisor are also
> killed).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
