Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 75F56F1AB for ; Fri, 29 Mar 2013 20:49:16 +0000 (UTC) Received: (qmail 23070 invoked by uid 500); 29 Mar 2013 20:49:16 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 23046 invoked by uid 500); 29 Mar 2013 20:49:16 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 23034 invoked by uid 99); 29 Mar 2013 20:49:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Mar 2013 20:49:16 +0000 Date: Fri, 29 Mar 2013 20:49:15 +0000 (UTC) From: "Roshan Punnoose (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-1224) Custom Thread Pool in BatchScanner MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617704#comment-13617704 ] Roshan Punnoose commented on ACCUMULO-1224: ------------------------------------------- Maybe the right answer is to have a Factory definition for creating threads that can be backed by a thread pool. It would implement isOpen and close methods. And any external implementations, even if they wrap a thread pool, would have to decide how to "close", whether that means to do a shutdownNow, or wait for threads to finish, etc. Where would a user specify the BatchConfig? In the Instance when it starts? Maybe it is just a Hadoop Configuration object that is wrapped with methods to add the thread pool factory class name, etc. Btw, this is probably not the right place to ask this, but how come the Connector class is a class and not an interface? Seems like there was probably a reason for this? (Instance too) > Custom Thread Pool in BatchScanner > ---------------------------------- > > Key: ACCUMULO-1224 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1224 > Project: Accumulo > Issue Type: Improvement > Components: client > Reporter: Roshan Punnoose > Assignee: Billie Rinaldi > Priority: Minor > Attachments: threadPool.patch > > > I would like the ability to supply my own ThreadPool(ExecutorService) when the BatchScanner is created. This would give me the ability to throttle how many threads are created in an application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira