[
https://issues.apache.org/jira/browse/STORM-2447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952493#comment-15952493
]
Jungtaek Lim commented on STORM-2447:
-------------------------------------
First of all, I really like the concept.
I feel we need to cover, or at least guide how to do it for current specific
use case: end-users run LocalCluster in IDE, and process (with topology) is
debuggable.
Is it a goal of this issue to "add" an option to run local cluster
transparently, so end-users can still do the same and handle above use case?
> Make local cluster transparent
> ------------------------------
>
> Key: STORM-2447
> URL: https://issues.apache.org/jira/browse/STORM-2447
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-core
> Affects Versions: 2.0.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
>
> As part of the work for STORM-2441. We would like to split the storm
> classpath down so the client jar only has what it needs. Everything else is
> in a separate classpath(s) for daemon processes. One of the issues with this
> is that local mode is built into almost all examples because it uses a
> separate API from the normal storm client API.
> To work around this we really should add in a new option to {{storm jar}}
> that will include everything on the classpath, set a SystemProperty and call
> into a special Main Method. The new main method will
> 1) start up the LocalCluster
> 2) configure SotrmSubmitter, NimbusClinet and DRPCClient to talk to the
> LocalCluster instead.
> 3) run the regular main method
> 4) optionally sleep for a configurable amount of time
> 5) shut down the local cluster.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
