You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Sanket Chintapalli (JIRA)" <ji...@apache.org> on 2015/04/14 20:09:13 UTC

[jira] [Comment Edited] (STORM-766) Supervisor summary should include the version.

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

Sanket Chintapalli edited comment on STORM-766 at 4/14/15 6:09 PM:
-------------------------------------------------------------------

Hi Parth,
I am a newbie and I found this topic interesting in Storm. I would like to contribute to this issue. I am looking forward to get some siters to solve the issue. I kind of figured out that I have to make changes to the thrift file, the supervisor heart beat function in supervisor.clj and update the ui to read the info. Let me know if I have to take care of any other classes.


was (Author: redsanket):
Hi Parth,
I am a newbie and I found this topic interesting in Storm. I would like to contribute to this issue. I am looking forward to get some siters to solve the issue. 

> Supervisor summary should include the version.
> ----------------------------------------------
>
>                 Key: STORM-766
>                 URL: https://issues.apache.org/jira/browse/STORM-766
>             Project: Apache Storm
>          Issue Type: Bug
>    Affects Versions: 0.10.0
>            Reporter: Parth Brahmbhatt
>            Assignee: Parth Brahmbhatt
>            Priority: Minor
>             Fix For: 0.10.0
>
>
> With the support for rolling upgrade, different nodes in the cluster can run different versions of storm. We should include the version in SupervisorSummary just like NimbusSummary so admins can identify nodes that needs upgrading/downgrading from UI. 
> As part of this change I will also add a supervisor/log link in the ui.



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