You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2017/03/31 02:12:41 UTC

[jira] [Created] (STORM-2441) Extract client (worker) side artifacts from 'storm-core'

Jungtaek Lim created STORM-2441:
-----------------------------------

             Summary: Extract client (worker) side artifacts from 'storm-core'
                 Key: STORM-2441
                 URL: https://issues.apache.org/jira/browse/STORM-2441
             Project: Apache Storm
          Issue Type: Improvement
          Components: storm-core
            Reporter: Jungtaek Lim
            Assignee: Jungtaek Lim


There were some interests for having client side artifacts or modularize Storm.

- STORM-30
- STORM-117

We have been having one huge artifact 'storm-core' for supporting all the things, and recently we extracted 'storm-drpc-server' due to dependency issue.

We also have been struggling to handle shade & relocation for lots artifacts, but in fact the artifacts which we need to relocate are just Worker related thing. So extracting worker and related classes into separate artifact and assigning different classpath in Storm cluster should help remedying.

We may still need to struggle with relocation, but the count of target artifacts should be much smaller.

Another thing we need to consider is LocalCluster, which pulls most of daemons but user topology still need to pull it. So we need to have separate artifact for LocalCluster (maybe also daemons without webapp).

Last, we need to consider about UI and Logviewer porting. Artifact 'storm-drpc-server' is not generic and I think we can group UI, Logviewer, DRPC (only http server) into this artifact. Artifact name should be changed then.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)