Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 13EBCFA85 for ; Tue, 2 Apr 2013 22:45:08 +0000 (UTC) Received: (qmail 1912 invoked by uid 500); 2 Apr 2013 22:45:07 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 1843 invoked by uid 500); 2 Apr 2013 22:45:07 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 1831 invoked by uid 99); 2 Apr 2013 22:45:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Apr 2013 22:45:07 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of elliott.neil.clark@gmail.com designates 209.85.212.179 as permitted sender) Received: from [209.85.212.179] (HELO mail-wi0-f179.google.com) (209.85.212.179) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Apr 2013 22:45:03 +0000 Received: by mail-wi0-f179.google.com with SMTP id hn17so951012wib.0 for ; Tue, 02 Apr 2013 15:44:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=3J5yATyaQo29oSAHad/VsGUJvf0tFdB4ysiI6nA05iA=; b=w+5PGftlvGzu4wguC5tmDvpXafpC1dDAJ+gsgNHE6zthbnskjAhMlXfl3HCPKpXo+n xSOxF4uMJWhRY+FZ4PCxWGNpGUq9IbZ6FMOUMDGczTwBTSP7PzIHNICzW8ZtrtthN69L Gg31jyFa+MQdITU1oGDD3B6QPYNLcHXGNEt5QLe6Top7JM5thStCPZmy3Wt4qni0yqob nEM58qiagL06zotlTORhkZSUi1CimzbtlXiWvPI0qv5WH8N6Dy81xPD/7XmLnH+5lPgK knbAv8XEIV8DNS+KerayQyjiyVNoxlilE/cdBYURCwj4OEOPmSD8bOIHoBUSu2g5TsJz +7ZQ== MIME-Version: 1.0 X-Received: by 10.180.81.232 with SMTP id d8mr19143280wiy.25.1364942681895; Tue, 02 Apr 2013 15:44:41 -0700 (PDT) Sender: elliott.neil.clark@gmail.com Received: by 10.194.26.129 with HTTP; Tue, 2 Apr 2013 15:44:41 -0700 (PDT) Date: Tue, 2 Apr 2013 15:44:41 -0700 X-Google-Sender-Auth: vAKD7tQt3XGzZlXNWNfYXWya8JM Message-ID: Subject: Shared ThreadPoolExecutor in HTable by default. From: Elliott Clark To: "dev@hbase.apache.org" Content-Type: multipart/alternative; boundary=f46d044401c2b17b4104d9687bf8 X-Virus-Checked: Checked by ClamAV on apache.org --f46d044401c2b17b4104d9687bf8 Content-Type: text/plain; charset=ISO-8859-1 Is there any reason that the ThreadPoolExecutor used in HTable[1] couldn't be a singleton. That would mean that by default htables share threads (as I would argue is correct), but still give advanced users the ability to override this using the more explicit[2] constructor. 1. https://github.com/apache/hbase/blob/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTable.java#L183 2. https://github.com/apache/hbase/blob/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTable.java#L202 Thanks --f46d044401c2b17b4104d9687bf8--