You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@storm.apache.org by "Ethan Li (Jira)" <ji...@apache.org> on 2020/01/03 16:17:00 UTC

[jira] [Closed] (STORM-3482) Implement One Worker Per Component Option

     [ https://issues.apache.org/jira/browse/STORM-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ethan Li closed STORM-3482.
---------------------------
    Fix Version/s: 2.2.0
       Resolution: Fixed

It was merged into master. Thanks [~dandsager]

> Implement One Worker Per Component Option
> -----------------------------------------
>
>                 Key: STORM-3482
>                 URL: https://issues.apache.org/jira/browse/STORM-3482
>             Project: Apache Storm
>          Issue Type: New Feature
>            Reporter: David Andsager
>            Assignee: David Andsager
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 2.2.0
>
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> User complaints saying that Storm is hard to debug, mainly because Storm runs executors from different components (spout, bolt) in a single JVM process.
> Adding an option that schedules executors from from a single component on a worker. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)