curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Alberth (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CURATOR-323) USe threadpool executor with prio queue
Date Fri, 06 May 2016 13:11:12 GMT
Rich Alberth created CURATOR-323:
------------------------------------

             Summary: 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)

Mime
View raw message