[
https://issues.apache.org/jira/browse/STORM-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503690#comment-14503690
]
ASF GitHub Bot commented on STORM-766:
--------------------------------------
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/529#issuecomment-94573682
I ran a simple manual test where I had an old supervisor and a new nimbus
and everything worked well. I am +1 for merging this in once the merge
conflict is resolved.
> 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: Sanket Chintapalli
> 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)
