You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/09/25 18:45:04 UTC

[jira] [Commented] (STORM-123) NImbus BCP

    [ https://issues.apache.org/jira/browse/STORM-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908297#comment-14908297 ] 

ASF GitHub Bot commented on STORM-123:
--------------------------------------

GitHub user 3Dragan opened a pull request:

    https://github.com/apache/storm/pull/763

    [STORM-123], add check case for external change of 'now' value.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/3Dragan/storm master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/storm/pull/763.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #763
    
----
commit 7d5285545a4d4f227f7f8616c2f769f055649560
Author: ddragan <dm...@gmail.com>
Date:   2015-09-25T14:58:07Z

    [STORM-123], add check case for external change of 'now' value.

commit cc082aa93e5da92c4c3f635420fabf8bb6e60bf3
Author: dragan <dm...@gmail.com>
Date:   2015-09-25T16:37:50Z

    add a comment description

----


> 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)