[ https://issues.apache.org/jira/browse/STORM-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908427#comment-14908427 ]
Parth Brahmbhatt edited comment on STORM-123 at 9/25/15 6:05 PM: ----------------------------------------------------------------- Given storm-166 is merged [~xumingming] do you think this is ok to resolve? was (Author: parth.brahmbhatt): Given storm-166 is checked [~xumingming] do you think this is ok to resolve? > 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)