You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@storm.apache.org by "Sharma, Prashant" <ps...@netsuite.com> on 2015/03/24 05:22:56 UTC
Topology Upgrade in Prod
Hi,
Since a Topology is supposed to run forever, How to introduce changes/upgrades to existing Topology.
Is the preferred way to Kill an existing Topology and drop a new jar with changes?
thanks,
Prashant Sharma
To learn more about SuiteWorld, visit
www.netsuite.com/suiteworld.
NOTICE: This email and any attachments may contain confidential and proprietary information of NetSuite Inc. and is for the sole use of the intended recipient for the stated purpose. Any improper use or distribution is prohibited. If you are not the intended recipient, please notify the sender; do not review, copy or distribute; and promptly delete or destroy all transmitted information. Please note that all communications and information transmitted through this email system may be monitored and retained by NetSuite or its agents and that all incoming email is automatically scanned by a third party spam and filtering service which may result in deletion of a legitimate e-mail before it is read by the intended recipient.
Re: Topology Upgrade in Prod
Posted by Nishu <ni...@gmail.com>.
Currently there is no provision of updating running topology directly .
You'll have to kill it first and then run it again.
You can refer Update Running Storm topology
<http://nishutayaltech.blogspot.in/2014/07/update-running-topology-on-storm-cluster.html>
blog
for the implementation.
-
Nishu
On Tue, Mar 24, 2015 at 12:38 PM, manish belsare <
manishbelsare2003@gmail.com> wrote:
> You need to run storm swap to upgrade the current executing topology. Pl
> check the storm site for deploying on remote cluster.
>
>
> On Tuesday, March 24, 2015, Andrew Xor <an...@gmail.com>
> wrote:
>
>> Yep, that's what I thought but since it was quite a while since I checked
>> that JIRA issue I was not aware of it's progress although... I didn't see
>> it in any of the release change logs so far thus I thought it was not yet
>> there.
>>
>> Regards,
>>
>> A.
>>
>> On Tue, Mar 24, 2015 at 7:22 AM, Parth Brahmbhatt <
>> pbrahmbhatt@hortonworks.com> wrote:
>>
>>> No its not and it will not be part of the upcoming 0.9.4 release as
>>> well, if you want this to be prioritized please vote for it. I have asked
>>> the developer who originally worked on providing this feature to up merge
>>> his changes to master , if he does not reply in a week I plan to start
>>> working on this jira.
>>>
>>> Currently the only way is to kill a topology and resubmit it with
>>> updated code.
>>>
>>> Thanks
>>> Parth
>>>
>>> From: Andrew Xor <an...@gmail.com>
>>> Reply-To: "user@storm.apache.org" <us...@storm.apache.org>
>>> Date: Monday, March 23, 2015 at 10:16 PM
>>> To: Harsha <st...@harsha.io>
>>> Cc: "user@storm.apache.org" <us...@storm.apache.org>
>>> Subject: Re: Topology Upgrade in Prod
>>>
>>> Yeah I am aware of this but as far as I know it's not included in any
>>> of the stable releases as of yet, is it?
>>>
>>>
>>
>
> --
> Manish
>
>
--
with regards,
Nishu Tayal
Re: Topology Upgrade in Prod
Posted by manish belsare <ma...@gmail.com>.
You need to run storm swap to upgrade the current executing topology. Pl
check the storm site for deploying on remote cluster.
On Tuesday, March 24, 2015, Andrew Xor <an...@gmail.com> wrote:
> Yep, that's what I thought but since it was quite a while since I checked
> that JIRA issue I was not aware of it's progress although... I didn't see
> it in any of the release change logs so far thus I thought it was not yet
> there.
>
> Regards,
>
> A.
>
> On Tue, Mar 24, 2015 at 7:22 AM, Parth Brahmbhatt <
> pbrahmbhatt@hortonworks.com
> <javascript:_e(%7B%7D,'cvml','pbrahmbhatt@hortonworks.com');>> wrote:
>
>> No its not and it will not be part of the upcoming 0.9.4 release as
>> well, if you want this to be prioritized please vote for it. I have asked
>> the developer who originally worked on providing this feature to up merge
>> his changes to master , if he does not reply in a week I plan to start
>> working on this jira.
>>
>> Currently the only way is to kill a topology and resubmit it with
>> updated code.
>>
>> Thanks
>> Parth
>>
>> From: Andrew Xor <andreas.grammenos@gmail.com
>> <javascript:_e(%7B%7D,'cvml','andreas.grammenos@gmail.com');>>
>> Reply-To: "user@storm.apache.org
>> <javascript:_e(%7B%7D,'cvml','user@storm.apache.org');>" <
>> user@storm.apache.org
>> <javascript:_e(%7B%7D,'cvml','user@storm.apache.org');>>
>> Date: Monday, March 23, 2015 at 10:16 PM
>> To: Harsha <storm@harsha.io
>> <javascript:_e(%7B%7D,'cvml','storm@harsha.io');>>
>> Cc: "user@storm.apache.org
>> <javascript:_e(%7B%7D,'cvml','user@storm.apache.org');>" <
>> user@storm.apache.org
>> <javascript:_e(%7B%7D,'cvml','user@storm.apache.org');>>
>> Subject: Re: Topology Upgrade in Prod
>>
>> Yeah I am aware of this but as far as I know it's not included in any
>> of the stable releases as of yet, is it?
>>
>>
>
--
Manish
Re: Topology Upgrade in Prod
Posted by Andrew Xor <an...@gmail.com>.
Yep, that's what I thought but since it was quite a while since I checked
that JIRA issue I was not aware of it's progress although... I didn't see
it in any of the release change logs so far thus I thought it was not yet
there.
Regards,
A.
On Tue, Mar 24, 2015 at 7:22 AM, Parth Brahmbhatt <
pbrahmbhatt@hortonworks.com> wrote:
> No its not and it will not be part of the upcoming 0.9.4 release as
> well, if you want this to be prioritized please vote for it. I have asked
> the developer who originally worked on providing this feature to up merge
> his changes to master , if he does not reply in a week I plan to start
> working on this jira.
>
> Currently the only way is to kill a topology and resubmit it with
> updated code.
>
> Thanks
> Parth
>
> From: Andrew Xor <an...@gmail.com>
> Reply-To: "user@storm.apache.org" <us...@storm.apache.org>
> Date: Monday, March 23, 2015 at 10:16 PM
> To: Harsha <st...@harsha.io>
> Cc: "user@storm.apache.org" <us...@storm.apache.org>
> Subject: Re: Topology Upgrade in Prod
>
> Yeah I am aware of this but as far as I know it's not included in any of
> the stable releases as of yet, is it?
>
>
Re: Topology Upgrade in Prod
Posted by Parth Brahmbhatt <pb...@hortonworks.com>.
No its not and it will not be part of the upcoming 0.9.4 release as well, if you want this to be prioritized please vote for it. I have asked the developer who originally worked on providing this feature to up merge his changes to master , if he does not reply in a week I plan to start working on this jira.
Currently the only way is to kill a topology and resubmit it with updated code.
Thanks
Parth
From: Andrew Xor <an...@gmail.com>>
Reply-To: "user@storm.apache.org<ma...@storm.apache.org>" <us...@storm.apache.org>>
Date: Monday, March 23, 2015 at 10:16 PM
To: Harsha <st...@harsha.io>>
Cc: "user@storm.apache.org<ma...@storm.apache.org>" <us...@storm.apache.org>>
Subject: Re: Topology Upgrade in Prod
Yeah I am aware of this but as far as I know it's not included in any of the stable releases as of yet, is it?
Re: Topology Upgrade in Prod
Posted by Andrew Xor <an...@gmail.com>.
Yeah I am aware of this but as far as I know it's not included in any of
the stable releases as of yet, is it?
Regards,
A.
<https://www.dropbox.com/s/2kcxe59zsi9nrdt/pgpsig.txt>
https://www.dropbox.com/s/ei2nqsen641daei/pgpsig.txt
On Tue, Mar 24, 2015 at 7:13 AM, Harsha <st...@harsha.io> wrote:
> There is a JIRA open on this feature
> https://issues.apache.org/jira/browse/STORM-167 .
>
> --
> Harsha
>
>
> On March 23, 2015 at 9:28:37 PM, Andrew Xor (andreas.grammenos@gmail.com)
> wrote:
>
> I think that's the only way of actually updating the code, since
> besides rebalancing Storm does not (yet) allow for topology "refresh"
> without first hard-restarting it; unless of course I am missing something
> major.
>
> Regards,
>
> A.
>
>
>
> On Tue, Mar 24, 2015 at 6:22 AM, Sharma, Prashant <ps...@netsuite.com>
> wrote:
>
>>
>> Hi,
>> Since a Topology is supposed to run forever, How to introduce
>> changes/upgrades to existing Topology.
>> Is the preferred way to Kill an existing Topology and drop a new jar with
>> changes?
>> thanks,
>> Prashant Sharma
>>
>>
>> [image: Suite World 2015] <http://www.netsuite.com/suiteworld>
>> To learn more about SuiteWorld, visit http://www.netsuitesuiteworld.com/
>> <http://www.netsuite.com/suiteworld>
>>
>> NOTICE: This email and any attachments may contain confidential and
>> proprietary information of NetSuite Inc. and is for the sole use of the
>> intended recipient for the stated purpose. Any improper use or distribution
>> is prohibited. If you are not the intended recipient, please notify the
>> sender; do not review, copy or distribute; and promptly delete or destroy
>> all transmitted information. Please note that all communications and
>> information transmitted through this email system may be monitored and
>> retained by NetSuite or its agents and that all incoming email is
>> automatically scanned by a third party spam and filtering service which may
>> result in deletion of a legitimate e-mail before it is read by the intended
>> recipient.
>>
>
>
Re: Topology Upgrade in Prod
Posted by Harsha <st...@harsha.io>.
There is a JIRA open on this feature https://issues.apache.org/jira/browse/STORM-167 .
--
Harsha
On March 23, 2015 at 9:28:37 PM, Andrew Xor (andreas.grammenos@gmail.com) wrote:
I think that's the only way of actually updating the code, since besides rebalancing Storm does not (yet) allow for topology "refresh" without first hard-restarting it; unless of course I am missing something major.
Regards,
A.
On Tue, Mar 24, 2015 at 6:22 AM, Sharma, Prashant <ps...@netsuite.com> wrote:
Hi,
Since a Topology is supposed to run forever, How to introduce changes/upgrades to existing Topology.
Is the preferred way to Kill an existing Topology and drop a new jar with changes?
thanks,
Prashant Sharma
To learn more about SuiteWorld, visit http://www.netsuitesuiteworld.com/
NOTICE: This email and any attachments may contain confidential and proprietary information of NetSuite Inc. and is for the sole use of the intended recipient for the stated purpose. Any improper use or distribution is prohibited. If you are not the intended recipient, please notify the sender; do not review, copy or distribute; and promptly delete or destroy all transmitted information. Please note that all communications and information transmitted through this email system may be monitored and retained by NetSuite or its agents and that all incoming email is automatically scanned by a third party spam and filtering service which may result in deletion of a legitimate e-mail before it is read by the intended recipient.
Re: Topology Upgrade in Prod
Posted by Andrew Xor <an...@gmail.com>.
I think that's the only way of actually updating the code, since besides
rebalancing Storm does not (yet) allow for topology "refresh" without first
hard-restarting it; unless of course I am missing something major.
Regards,
A.
On Tue, Mar 24, 2015 at 6:22 AM, Sharma, Prashant <ps...@netsuite.com>
wrote:
>
> Hi,
> Since a Topology is supposed to run forever, How to introduce
> changes/upgrades to existing Topology.
> Is the preferred way to Kill an existing Topology and drop a new jar with
> changes?
> thanks,
> Prashant Sharma
>
>
> [image: Suite World 2015] <http://www.netsuite.com/suiteworld>
> To learn more about SuiteWorld, visit http://www.netsuitesuiteworld.com/
> <http://www.netsuite.com/suiteworld>
>
> NOTICE: This email and any attachments may contain confidential and
> proprietary information of NetSuite Inc. and is for the sole use of the
> intended recipient for the stated purpose. Any improper use or distribution
> is prohibited. If you are not the intended recipient, please notify the
> sender; do not review, copy or distribute; and promptly delete or destroy
> all transmitted information. Please note that all communications and
> information transmitted through this email system may be monitored and
> retained by NetSuite or its agents and that all incoming email is
> automatically scanned by a third party spam and filtering service which may
> result in deletion of a legitimate e-mail before it is read by the intended
> recipient.
>