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

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

Github user revans2 commented on a diff in the pull request:

    https://github.com/apache/storm/pull/746#discussion_r40729530
  
    --- Diff: storm-core/src/clj/backtype/storm/daemon/nimbus.clj ---
    @@ -308,15 +308,15 @@
     (defn- all-supervisor-info
       ([storm-cluster-state] (all-supervisor-info storm-cluster-state nil))
       ([storm-cluster-state callback]
    -     (let [supervisor-ids (.supervisors storm-cluster-state callback)]
    -       (into {}
    -             (mapcat
    -              (fn [id]
    -                (if-let [info (.supervisor-info storm-cluster-state id)]
    -                  [[id info]]
    -                  ))
    -              supervisor-ids))
    -       )))
    +    (let [supervisor-ids (.supervisors storm-cluster-state callback)]
    +      (into {}
    +        (mapcat
    +          (fn [id]
    +            (if-let [info (.supervisor-info storm-cluster-state id)]
    +              [[id info]]
    +              ))
    +          supervisor-ids))
    +      )))
    --- End diff --
    
    If this is just white space changes I think we should probably revert them


> Resource Aware Scheduling
> -------------------------
>
>                 Key: STORM-893
>                 URL: https://issues.apache.org/jira/browse/STORM-893
>             Project: Apache Storm
>          Issue Type: Umbrella
>            Reporter: Robert Joseph Evans
>            Assignee: Boyang Jerry Peng
>         Attachments: resource_aware_scheduler_api.pdf
>
>
> At Yahoo we have been working on resource aware scheduling in storm, based 
> off of some work done in academia.  This rollup ticket is to track the 
> complete project.  With several sub tasks.  Some that are already done and 
> need to be pushed back, and others that we have not started on yet.



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

Reply via email to