[
https://issues.apache.org/jira/browse/STORM-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502879#comment-14502879
]
ASF GitHub Bot commented on STORM-766:
--------------------------------------
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/529#issuecomment-94460394
Overall the code looks good. The trick with the rolling upgrade is that we
want to be sure that an old nimbus can work with a new supervisor and a new
nimbus can work with an old supervisor too. Similarly for the client. An old
client should be able to work with a new nimbus and a new client should, in
most cases, work with an old nimbus. Perhaps the simples way to do this is to
provide a default value for version which is set to something like "VERSION NOT
PROVIDED".
> 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)
