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

Posted to issues@storm.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/03/11 23:11:00 UTC

[jira] [Updated] (STORM-3585) Change ConstraintSolverStrategy to allow max co-Location Count for spreading components

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

ASF GitHub Bot updated STORM-3585:
----------------------------------
    Labels: pull-request-available  (was: )

> Change ConstraintSolverStrategy to allow max co-Location Count for spreading components
> ---------------------------------------------------------------------------------------
>
>                 Key: STORM-3585
>                 URL: https://issues.apache.org/jira/browse/STORM-3585
>             Project: Apache Storm
>          Issue Type: New Feature
>          Components: storm-server
>    Affects Versions: 2.2.0
>            Reporter: Bipin Prasad
>            Assignee: Bipin Prasad
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 2.2.0
>
>
> We need constraint solver strategy to evolve around to using Map<Component, maxCoLocationCount> instead of simple list of components that get maximum of 1 collocation as specified in config _topology.spread.components_.



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