Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B118810673 for ; Mon, 18 Nov 2013 17:17:25 +0000 (UTC) Received: (qmail 77427 invoked by uid 500); 18 Nov 2013 17:17:23 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 77265 invoked by uid 500); 18 Nov 2013 17:17:23 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 76695 invoked by uid 99); 18 Nov 2013 17:17:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Nov 2013 17:17:22 +0000 Date: Mon, 18 Nov 2013 17:17:22 +0000 (UTC) From: "Nicolas Liochon (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-9990) RpcRetryingCallerFactory uses the conf for each "newCaller" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Nicolas Liochon created HBASE-9990: -------------------------------------- Summary: RpcRetryingCallerFactory uses the conf for each "newCaller" Key: HBASE-9990 URL: https://issues.apache.org/jira/browse/HBASE-9990 Project: HBase Issue Type: Bug Components: Client Affects Versions: 0.96.0, 0.98.0 Reporter: Nicolas Liochon Assignee: Nicolas Liochon Fix For: 0.98.0, 0.96.1 You can construct a RpcRetryingCallerFactory, but actually the conf is read for each call. Reading the conf is obviously expensive, and a profiling session shows it. If we want to sent hundreds of thousands of queries per second, we should not do that. RpcRetryingCallerFactory.newCaller is called for each get, for example. -- This message was sent by Atlassian JIRA (v6.1#6144)