Re: How to redeploy the topology

[Stephen Powis]

You would need to stop or kill the running topology first.  There is an
argument to the stop command that tells storm how long (in secs) to wait
before killing the topology.  My understanding of how this works is when
you issue the stop command, the topology simply disables the spouts in the
topology so no NEW tuples will be ingested at the top of the topology.
Then after your supplied timeout seconds, storm will actually kill the
topology.  The theory being that all of the tuples already being processed
within the topology should finish their processing completely within that
time window, and by the time it gets killed off, the topology is just
sitting idle.  Then you deploy your new version, and the spouts start
ingesting new tuples, and away you go.



On Tue, Jan 19, 2016 at 11:49 PM, Noppanit Charassinvichai <
noppani...@gmail.com> wrote:

> Right now I'm using storm jar command to deploy the topology to the storm
> cluster. I have setup Jenkins to deploy the code. However, if I want to
> redeploy again how can I deploy to not interrupt the current streaming
> because I would get the error saying the topology name already exists?
>
> Thanks
>

Re: How to redeploy the topology

[Noppanit Charassinvichai]

Doh! I totally miss this.
http://storm.apache.org/documentation/Command-line-client.html

On Tue, 19 Jan 2016 at 13:22 Noppanit Charassinvichai 
wrote:

> How can I tell storm to stop the current topology from command line?
> Ultimately, I want to automate the process.
>
> On Tue, 19 Jan 2016 at 13:00 Stephen Powis  wrote:
>
>> You would need to stop or kill the running topology first.  There is an
>> argument to the stop command that tells storm how long (in secs) to wait
>> before killing the topology.  My understanding of how this works is when
>> you issue the stop command, the topology simply disables the spouts in the
>> topology so no NEW tuples will be ingested at the top of the topology.
>> Then after your supplied timeout seconds, storm will actually kill the
>> topology.  The theory being that all of the tuples already being processed
>> within the topology should finish their processing completely within that
>> time window, and by the time it gets killed off, the topology is just
>> sitting idle.  Then you deploy your new version, and the spouts start
>> ingesting new tuples, and away you go.
>>
>>
>>
>> On Tue, Jan 19, 2016 at 11:49 PM, Noppanit Charassinvichai <
>> noppani...@gmail.com> wrote:
>>
>>> Right now I'm using storm jar command to deploy the topology to the
>>> storm cluster. I have setup Jenkins to deploy the code. However, if I want
>>> to redeploy again how can I deploy to not interrupt the current streaming
>>> because I would get the error saying the topology name already exists?
>>>
>>> Thanks
>>>
>>
>>

Re: How to redeploy the topology

[Noppanit Charassinvichai]

How can I tell storm to stop the current topology from command line?
Ultimately, I want to automate the process.

On Tue, 19 Jan 2016 at 13:00 Stephen Powis  wrote:

> You would need to stop or kill the running topology first.  There is an
> argument to the stop command that tells storm how long (in secs) to wait
> before killing the topology.  My understanding of how this works is when
> you issue the stop command, the topology simply disables the spouts in the
> topology so no NEW tuples will be ingested at the top of the topology.
> Then after your supplied timeout seconds, storm will actually kill the
> topology.  The theory being that all of the tuples already being processed
> within the topology should finish their processing completely within that
> time window, and by the time it gets killed off, the topology is just
> sitting idle.  Then you deploy your new version, and the spouts start
> ingesting new tuples, and away you go.
>
>
>
> On Tue, Jan 19, 2016 at 11:49 PM, Noppanit Charassinvichai <
> noppani...@gmail.com> wrote:
>
>> Right now I'm using storm jar command to deploy the topology to the storm
>> cluster. I have setup Jenkins to deploy the code. However, if I want to
>> redeploy again how can I deploy to not interrupt the current streaming
>> because I would get the error saying the topology name already exists?
>>
>> Thanks
>>
>
>

Re: How to redeploy the topology

[Matthias J. Sax]

That is not possible.

You first need to "kill" the running topology, and then resubmit with
the new code...

-Matthias

On 01/19/2016 05:49 PM, Noppanit Charassinvichai wrote:
> Right now I'm using storm jar command to deploy the topology to the
> storm cluster. I have setup Jenkins to deploy the code. However, if I
> want to redeploy again how can I deploy to not interrupt the current
> streaming because I would get the error saying the topology name already
> exists? 
> 
> Thanks



signature.asc
Description: OpenPGP digital signature