You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Robert Joseph Evans (JIRA)" <ji...@apache.org> on 2016/03/29 18:37:25 UTC

[jira] [Resolved] (STORM-1634) Minor Refactoring of Resource Aware Scheduler

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

Robert Joseph Evans resolved STORM-1634.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0

Thanks [~jerrypeng],

I merged this into master and 1.x-branch

> Minor Refactoring of Resource Aware Scheduler
> ---------------------------------------------
>
>                 Key: STORM-1634
>                 URL: https://issues.apache.org/jira/browse/STORM-1634
>             Project: Apache Storm
>          Issue Type: Improvement
>            Reporter: Boyang Jerry Peng
>            Assignee: Boyang Jerry Peng
>            Priority: Minor
>             Fix For: 1.0.0
>
>
> Refactored the following:
> 1.  The API interface to define custom scheduling strategies. The API exposed from RAS to a per topology scheduling strategy is messy and needs to be cleaned up.
> 2. In RAS, the state of the scheduler is held by several member variables.  Its cleaner if the scheduler state is represented by a single object.  This will help we reduce the amount of code need when checkpointing the state of the scheduler and potentially restoring the state in the future when a bad scheduling happens



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)