You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Rich Alberth (JIRA)" <ji...@apache.org> on 2016/05/06 15:08:13 UTC

[jira] [Updated] (CURATOR-323) Use threadpool executor with prio queue

     [ https://issues.apache.org/jira/browse/CURATOR-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rich Alberth updated CURATOR-323:
---------------------------------
    Summary: Use threadpool executor with prio queue  (was: USe threadpool executor with prio queue)

> Use threadpool executor with prio queue
> ---------------------------------------
>
>                 Key: CURATOR-323
>                 URL: https://issues.apache.org/jira/browse/CURATOR-323
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Recipes
>    Affects Versions: 2.10.0
>            Reporter: Rich Alberth
>
> (couldn't find a forum link to ask this question, trying here, please advise if this is not the right venue)
> I'm creating a priority queue in Spring appcontext.xml, and wiring a thread pool object as the executor.  My intention is to have a single Curator framework connection, a single priority queue object, and a thread pool to control parallel execution.  My hope is as elements are dequeued, they would be given to the thread pool, which would be responsible for executing them in parallel.  I'm not using a lock with the queue.
> From testing, a single thread is always used, regardless of my executor.
> Can you confirm this is intended?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)