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

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

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

    https://github.com/apache/storm/pull/875#discussion_r44554722
  
    --- Diff: storm-core/src/ui/public/templates/index-page-template.html ---
    @@ -215,6 +215,26 @@
             </span>
           </th>
           <th>
    +        <span data-toggle="tooltip" data-placement="above" title="Memory 
capacity of a supervisor.">
    +          Total Mem (MB)
    +        </span>
    +      </th>
    +      <th>
    +        <span data-toggle="tooltip" data-placement="left" title="Memory 
that has been allocated.">
    +          Used Mem (MB)
    +        </span>
    +      </th>
    +      <th>
    +        <span data-toggle="tooltip" data-placement="above" title="CPU 
capacity of a supervisor. Every 100 means one core.">
    +          Total CPU (%)
    +        </span>
    +      </th>
    +      <th>
    +        <span data-toggle="tooltip" data-placement="left" title="CPU that 
has been allocated. Every 100 means one core">
    +          Used CPU (%)
    --- End diff --
    
    Same here


> Web UI to show resource usages and Total Resources on all supervisors
> ---------------------------------------------------------------------
>
>                 Key: STORM-1198
>                 URL: https://issues.apache.org/jira/browse/STORM-1198
>             Project: Apache Storm
>          Issue Type: Story
>          Components: storm-core
>            Reporter: Zhuo Liu
>            Assignee: Zhuo Liu
>            Priority: Minor
>         Attachments: supervisor-resources.png
>
>
> As we have resource aware scheduler (STORM-894), we want to be able to 
> display resource capacity (CPU, memory; and network in future) and scheduled 
> resource usage on each supervisor node.



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

Reply via email to