streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Hager [W2O Group]" <>
Subject Re: LocalStreamBuilder#stop()
Date Wed, 08 Oct 2014 19:19:39 GMT
I guess the difference is that a ThreadPool Executor has a different

These are essentially the equivalents
Shutdown() <― Turn off providers Timeout(infinite)
Shutdown(long) <― Turn off Providers - Timeout(userSpecified)

ShutdownNow() <― Turn off providers, clear any items in queue, await
termination (INF timeout)
ShutdownNow(long) <― Turn off providers, clear any items in queue, kill
threads if not satisfied by the user specified long.

The behaviors are slightly different… but critical in terms of how one
would manager their shutdown.

In an ideal world, a user might want to turn it off, but get everything
out, if they can. If they can’t in say, 5 minutes, they decide to be more
aggressive and are willing to abort tasks, kill threads, whatever it takes
to turn it off.

It is like trying to turn off your alarm clock in the morning, hitting the
button, hitting hit hard, then finally ripping it from the wall and
throwing it across the room without regard for the safety of the alarm
clock. :-)


On 10/8/14, 2:07 PM, "Ryan Ebanks" <> wrote:

>@Matt Hager
>You are describing exactly what we are talking about in the options.
>Option 1  would be the equivalent of calling shutdown with an infinite
>timeout.  Option 2 would be calling shutdownNow with a very small timeout.
>And option 2b would be calling shutdown with a predefined timeout and then
>calling shutdownNow if the tasks hadn't terminated at the end of the
>-Ryan Ebanks
>On Wed, Oct 8, 2014 at 10:34 AM, Matthew Hager [W2O Group] <
>> wrote:
>> Terminating threads is never a good idea. Shutdown the providers, give
>> user an option to set a wait-out time. Default should be 10 minutes or
>> something.
>> I¹d pattern it off something like the way that ThreadPoolExecutor¹s
>> termination behavior works. (Essentially, that is what you are doing)
>> Thanks!
>> Matt
>> On 10/8/14, 10:31 AM, "Ryan Ebanks" <> wrote:
>> >I've been added tests and fixing some issues in the local stream
>> >class.  I need some input on how the stop() method should work so I can
>> >write the appropriate tests.
>> >
>> >Option 1.) Gentle Shutdown
>> >Immediately stop the providers from producing more data, but allow for
>> >data currently in the stream to finish processing.  Shutdown time
>>would be
>> >unknown as a result.
>> >
>> >Option 2.) Forceful Shutdown
>> >Immediately stop the providers from producing more data, and stop all
>> >processors/writers.  Data will be left in the pipeline will be
>> >shutdown will be immediate
>> >
>> >Option 2b) Forceful Shutdown after small wait
>> >Immediately stop providers from producing more data.  Give the
>> >processors/writers a small window to try to finish processing (<
>> >and if not finished, forcefully shutdown all processors/writers.
>> >
>> >
>> >These options can be changed in the future as more features are added.
>> >For
>> >example once datum tracking is implemented, we will probably want a
>> >combination of option 1 and 2b.  But we need a defined way for it work
>> >now,
>> >so tests are testing the correct functionality.
>> >
>> >-Ryan Ebanks

View raw message