curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CURATOR-323) Use threadpool executor with prio queue
Date Sat, 21 May 2016 17:48:13 GMT

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

Jordan Zimmerman resolved CURATOR-323.
--------------------------------------
    Resolution: Invalid

Curator uses mailing lists for discussions. This is more appropriate for these: http://curator.apache.org/mail-lists.html

The short answer is that you only need 1 Curator instance per cluster you are connected to.

> 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