Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 251DFD2B9 for ; Tue, 25 Jun 2013 13:37:27 +0000 (UTC) Received: (qmail 58497 invoked by uid 500); 25 Jun 2013 13:37:24 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 58449 invoked by uid 500); 25 Jun 2013 13:37:23 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 58436 invoked by uid 99); 25 Jun 2013 13:37:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jun 2013 13:37:23 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [209.85.128.179] (HELO mail-ve0-f179.google.com) (209.85.128.179) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jun 2013 13:37:17 +0000 Received: by mail-ve0-f179.google.com with SMTP id d10so10062586vea.38 for ; Tue, 25 Jun 2013 06:36:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=FEy+OqxUZ9RTUb8PoC7XHLRiPl44ormicdGipG1pl58=; b=gqH75v178nEWW/8ei4yR70NSOfKaSiNCZVq9RAjuM2jiZxRchYphaRIHGHp6WqiAcG //j35DCWu5Ut7iCFX2GIwetLZtxEV8r1AkVL7TUhzocETs6tA6DyuY/wvU3/BqNGVe3D UCMoueKnPLPMlIOwUhxxtLLlBDzAbw+ixy8zIAEui3v+uObPXUWW4W7dKvNy43XMaeWh Ir4gcF9KVpi9W7+kMGXKYnfdOHWTmks/fDUNcqf3VLp9hYGP+RTyj3xR4YmcDqq3L7hI Qc2Ulp6a0qgwBCjxJ9FXfu7DDLEOZnq0oUbIDlx0YDXg1I7OoVsyo06sZ6zt6y+3v0zT oS5w== X-Received: by 10.220.112.16 with SMTP id u16mr13585825vcp.40.1372167396377; Tue, 25 Jun 2013 06:36:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.111.169 with HTTP; Tue, 25 Jun 2013 06:36:16 -0700 (PDT) In-Reply-To: References: From: Jean-Marc Spaggiari Date: Tue, 25 Jun 2013 09:36:16 -0400 Message-ID: Subject: Re: HBase Multiget taking more time To: user@hbase.apache.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQnA5q85o4BExe8Ngc3VMKcTR4GhvLdwoY5AdwcZJxGXrgUipiHTf2PBHIHAZZK1Jy/xTFrC X-Virus-Checked: Checked by ClamAV on apache.org Hi Ankit, Attachements are not working well with the mailing list. Can you post them on pastbin? Also, can you please post the servers (region and master) logs? thanks, JM 2013/6/25 Ankit Jain : > Hi Jean-Marc/Michael, > > Thanks for the reply. > > Hardware detail: > Processor: 8 core > RAM: 16 GB. > > We have allotted 4GB of RAM to HBase and also we are ingesting data into > HBase in parallel with rate of 50 records(Each record has 20 KB) per sec. > > Please find the attached GC log. > > Thanks, > Ankit > > > On Tue, Jun 25, 2013 at 6:03 PM, Ankit Jain wrote: >> >> Hi Jean-Marc/Michael, >> >> Thanks for the reply. >> >> Hardware detail: >> Processor: 8 core >> RAM: 16 GB. >> >> We have allotted 4GB of RAM to HBase and also we are ingesting data into >> HBase in parallel with rate of 50 records(Each record has 20 KB) per sec. >> >> Please find the attached GC log. >> >> Thanks, >> Ankit >> >> >> >> >> >> >> On Tue, Jun 25, 2013 at 5:43 PM, Michael Segel >> wrote: >>> >>> Double your timeout from 60K to 120K. >>> While I don't think its the problem... its just a good idea. >>> >>> What happens if you drop the 50 down to 25? Do you still fail? >>> If not, go to 35, etc... until you hit a point where you fail. >>> >>> As Jean-Marc said, we need a bit more information. Including some >>> hardware info too. >>> >>> Thx >>> >>> -Mike >>> >>> On Jun 25, 2013, at 4:03 AM, Ankit Jain wrote: >>> >>> > Hi All, >>> > >>> > HBase multiget call taking large time and throwing time out exception. >>> > I am >>> > retrieving only 50 records in one call. The size of each record is 20 >>> > KB. >>> > >>> > java.net.SocketTimeoutException: 60000 millis timeout while waiting for >>> > channel to be ready for read. ch : >>> > java.nio.channels.SocketChannel[connected >>> > local=/192.168.50.122:48695remote=ct-0096/ >>> > 192.168.50.177:60020] >>> > >>> > hTable = new HTable(conf, tableName); >>> > results = hTable.get(rows); >>> > >>> > Cluster Detail: >>> > 1 master, 1 regionserver and 8 regions >>> > >>> > -- >>> > Thanks, >>> > Ankit Jain >>> >> >> >> >> -- >> Thanks, >> Ankit Jain > > > > > -- > Thanks, > Ankit Jain