Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 325912009A0 for ; Sat, 21 May 2016 19:48:19 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 31054160A04; Sat, 21 May 2016 17:48:19 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 9FF44160A02 for ; Sat, 21 May 2016 19:48:18 +0200 (CEST) Received: (qmail 45229 invoked by uid 500); 21 May 2016 17:48:13 -0000 Mailing-List: contact dev-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@curator.apache.org Delivered-To: mailing list dev@curator.apache.org Received: (qmail 45204 invoked by uid 99); 21 May 2016 17:48:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 May 2016 17:48:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 0431C2C1F6E for ; Sat, 21 May 2016 17:48:13 +0000 (UTC) Date: Sat, 21 May 2016 17:48:13 +0000 (UTC) From: "Jordan Zimmerman (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CURATOR-323) Use threadpool executor with prio queue MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 21 May 2016 17:48:19 -0000 [ 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)