Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 36926 invoked from network); 17 Feb 2009 18:51:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Feb 2009 18:51:04 -0000 Received: (qmail 37015 invoked by uid 500); 17 Feb 2009 18:51:02 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 36995 invoked by uid 500); 17 Feb 2009 18:51:02 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 36984 invoked by uid 99); 17 Feb 2009 18:51:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Feb 2009 10:51:02 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of saint.ack@gmail.com designates 209.85.217.170 as permitted sender) Received: from [209.85.217.170] (HELO mail-gx0-f170.google.com) (209.85.217.170) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Feb 2009 18:50:53 +0000 Received: by gxk18 with SMTP id 18so4299696gxk.5 for ; Tue, 17 Feb 2009 10:50:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=noRgkd2Z+hYz36CkLszgn7A5sCvkQOunnKAyPw8LtYU=; b=Wnk2xJ45cYGeIF7U8CPM0dAc13F67CDuBhi5LTeUIsmkmaYfI0xmatgJH9kMgKtwux jfvBg4ZD7aSC+gFVdPCP2v4PtioSfQiySUYSuOlXpnHzXhaw368la6MuM+11xxBjd88d ZtAlFKStJH4OtYYCgFmUajpwQC4fS0A7qXzSg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=T/OClfhMRU/vvV4RnRfsd87U7yaGeUDOyI8cx3VCaOApfPWDqX40p5EhSHbX7YI9Cs qMxhGLEoNElSn9zjvWiNylD2zkKjyy8ydJphYcUkC41QMWlIgalGxOB0efAkC2qvf5aw Va2cvpQGSqmtE+J1Ddw+UKTYBXpOFHMQll6sM= MIME-Version: 1.0 Sender: saint.ack@gmail.com Received: by 10.100.133.2 with SMTP id g2mr535372and.134.1234896632546; Tue, 17 Feb 2009 10:50:32 -0800 (PST) In-Reply-To: <534ab810902170931y50908c69mdbf925cf7ffdc3f4@mail.gmail.com> References: <534ab810902170931y50908c69mdbf925cf7ffdc3f4@mail.gmail.com> Date: Tue, 17 Feb 2009 10:50:32 -0800 X-Google-Sender-Auth: 04b424a892709f97 Message-ID: <7c962aed0902171050y1102230id39d3ed9ab8cffa@mail.gmail.com> Subject: Re: Parrallel reads on hbase From: stack To: hbase-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=0016e644c2ce1e03e7046321c718 X-Virus-Checked: Checked by ClamAV on apache.org --0016e644c2ce1e03e7046321c718 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit To create multiple instances, just instantiate multiple versions of HTable in your client -- one per thread. For an example, see the doMultipleClients method in this script: http://jukka.zitting.name/git/?p=hbase.git;a=blob_plain;f=src/test/org/apache/hadoop/hbase/PerformanceEvaluation.java;hb=0.19. Parallelism will go up if you have many servers with your table distributed across them. St.Ack On Tue, Feb 17, 2009 at 9:31 AM, shourabh rawat wrote: > Is it possible to perform parallel reads in hbase. > I m using parallel threads to do a get to the hbase. > Would it improve the hbase read performance. Would these threads run > in paralle or will the hbase run them sequentially. > Any other way that it is possible to perform parallel reads. > --0016e644c2ce1e03e7046321c718--