[
https://issues.apache.org/jira/browse/CURATOR-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812486#comment-13812486
]
Colin Morelli edited comment on CURATOR-27 at 11/3/13 9:02 PM:
---------------------------------------------------------------
What's the status on a 2.3.0 release (or snapsho)? Is it possible to back port
this onto the existing 2.2.0-incubating? Or, is there an easy workaround
without modifying source that could work temporarily?
was (Author: cmorelli):
What's the status on a 2.3.0 release (or snapshot release)? Is it possible to
back port this onto the existing 2.2.0-incubating? Or, is there an easy
workaround without modifying source that could work temporarily?
> PathChildrenCache creates but doesn't shut down Executors
> ---------------------------------------------------------
>
> Key: CURATOR-27
> URL: https://issues.apache.org/jira/browse/CURATOR-27
> Project: Apache Curator
> Issue Type: Bug
> Components: Recipes
> Affects Versions: 2.0.1-incubating
> Reporter: Ioannis Canellos
> Assignee: Ioannis Canellos
> Fix For: 2.3.0
>
> Attachments: CURATOR-27.patch
>
>
> After the introduction of the CloseableExecutorService (see CURATOR-17) the
> PathChildrenCache may create Executor services that it doesn't close.
> Ideally, the CloseableExecutorService should accept a parameter that
> specifies if the executor needs to be shutdown on close. Recipes that create
> their own ExecutorService should set this parameter to true. When an executor
> not directly managed by the recipe is used, the flag should be just false, so
> that the the executor doesn't always close (satisfy CURATOR-17).
--
This message was sent by Atlassian JIRA
(v6.1#6144)