[
https://issues.apache.org/jira/browse/STORM-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14496228#comment-14496228
]
Sanket Chintapalli edited comment on STORM-766 at 4/15/15 2:32 PM:
-------------------------------------------------------------------
Thanks Parth, that will really help me. I will work today until the end of this
week and hope I contribute my first patch. Let me know if there is any SLA for
this JIRA. I guess it is a minor one so I might take a bit more time to solve
my first patch.
was (Author: redsanket):
Thanks Parth, that will really help me. I will work on today until the end of
this week and hope I contribute my first patch. Let me know if there is any SLA
for this JIRA. I guess it is a minor one so I might take a bit more time to
solve my first patch.
> 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)
