You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Robert Joseph Evans (JIRA)" <ji...@apache.org> on 2017/12/20 16:45:01 UTC

[jira] [Resolved] (STORM-2837) RAS Constraint Solver Strategy

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

Robert Joseph Evans resolved STORM-2837.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

I merged this into master.

> RAS Constraint Solver Strategy
> ------------------------------
>
>                 Key: STORM-2837
>                 URL: https://issues.apache.org/jira/browse/STORM-2837
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>              Labels: pull-request-available
>             Fix For: 2.0.0
>
>          Time Spent: 4h
>  Remaining Estimate: 0h
>
> We have a use case where a user has some old native code and they need it to work with storm, but sadly the code is not thread safe so they need to be sure that each instance of a specific bolt is in a worker without other instances of the same bolt.  It also cannot co-exist with other bolts for a similar reason.  I know that this is a fairly strange use case, but to help fix the issue we wrote a strategy for RAS that can do a simple search of the state space trying to honor these constrains and we thought it best to push it back then to keep it internal.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)