[ 
https://issues.apache.org/jira/browse/STORM-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198288#comment-15198288
 ] 

ASF GitHub Bot commented on STORM-1634:
---------------------------------------

GitHub user jerrypeng opened a pull request:

    https://github.com/apache/storm/pull/1224

    [STORM-1634] - Minor Refactoring of Resource Aware Scheduler

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jerrypeng/storm ras_refactor

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/storm/pull/1224.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1224
    
----
commit ac5a8fb695bb2a31e3907be5f0204357e5440d53
Author: Boyang Jerry Peng <[email protected]>
Date:   2016-03-16T20:27:41Z

    [STORM-1634] -      Minor Refactoring of Resource Aware Scheduler

----


> 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
>
> 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)

Reply via email to