[
https://issues.apache.org/jira/browse/STORM-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908327#comment-14908327
]
ASF GitHub Bot commented on STORM-123:
--------------------------------------
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/763#issuecomment-143283874
It looks good to me I am +1 on the change, but I would like to hear from
others too.
> NImbus BCP
> ----------
>
> Key: STORM-123
> URL: https://issues.apache.org/jira/browse/STORM-123
> Project: Apache Storm
> Issue Type: Wish
> Reporter: James Xu
> Priority: Minor
>
> https://github.com/nathanmarz/storm/issues/737
> Hi,
> We are building a system where we need to have a BCP for nimbus box.
> Topologies will already be deployed on nimbus1 box while nimbus2 is our BCP.
> If nimbus1 goes down due to hardware failure how do get nimbus2 in so that we
> can control the start/kill of the topologies which were already deployed on
> nimbus1. I understand that topologies deployed earlier will continue to run
> since the jars have already been distributed to the supervisors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
