Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 30590 invoked from network); 3 Jul 2009 06:10:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Jul 2009 06:10:59 -0000 Received: (qmail 38954 invoked by uid 500); 3 Jul 2009 06:11:09 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 38904 invoked by uid 500); 3 Jul 2009 06:11:09 -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 38894 invoked by uid 99); 3 Jul 2009 06:11:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Jul 2009 06:11:09 +0000 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 nitayj@gmail.com designates 74.125.92.26 as permitted sender) Received: from [74.125.92.26] (HELO qw-out-2122.google.com) (74.125.92.26) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Jul 2009 06:10:59 +0000 Received: by qw-out-2122.google.com with SMTP id 8so895999qwh.35 for ; Thu, 02 Jul 2009 23:10:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=ULvk+jhYIVpEvqLNeieh0SfbYz8t08PKqQPtvNp4zfE=; b=bUskZcM+J3Abi3tj2FXtQjw6xRpEHKJ7z199PM4ixlU1hbwwUulcz6PBmr7LH6op6F NXer/B5WBxwVdZdQbtYCOuezH2yvFB/cnjSIVTipcD6D2SPLTmPZ1ytdbCe4gCTU3Y0Y JGj+esGHaxJYM5Sn29u8bXIT62ft+2/ozokzM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=W1J/pfqHiopJTG4v1zKz/HZ3zr0nHLh5JWQisAR5RIXuM/tZ9hPHhaw4OSu0vEammz 6FkGIxue5m2Cytp644vnxSEFS1gCgDVOO9+FfWOK172jWKHvtgVzN6A4dg57w/UTzdW9 ajE/UOKfLvBwmmLw6igHst/jHR+AAkj7bwxT4= MIME-Version: 1.0 Received: by 10.224.37.76 with SMTP id w12mr1355136qad.66.1246601438662; Thu, 02 Jul 2009 23:10:38 -0700 (PDT) In-Reply-To: References: Date: Thu, 2 Jul 2009 23:10:38 -0700 Message-ID: <82b0992a0907022310l550ff6d4p25abea9ada63aefe@mail.gmail.com> Subject: Re: Does HBASE allow multiple clients write to the same table? From: Nitay To: hbase-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=0015175cb498ed9222046dc703bd X-Virus-Checked: Checked by ClamAV on apache.org --0015175cb498ed9222046dc703bd Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Fleming, That warning is harmless. It should recover after such things. If you ever see some fatal problems (crashes, data loss, corruption, etc) after such a thing let us know. HBase should handle multiple clients writing to the same table fine. You will get better performance if they are writing to different regions (i.e. random data), as then the load is split between multiple region serving nodes. -n On Thu, Jul 2, 2009 at 9:28 PM, wrote: > Hi there, > > Now I use HTable to put my oracle table data to HBASE. > In order to enhance the speed, I create a few HTable clients to put the > data. > It occured only some WARN like "WARN zookeeper.ClientCnxn: Exception > closing session", > not fetal error,evently I found there's no data increase in HBASE. > Any HBASE setting about the client connection limitation? > Or HBASE doesn't allow multiple clients write to the same table. > Any suggestion? > Thank you > > Fleming > > --------------------------------------------------------------------------- > TSMC PROPERTY > This email communication (and any attachments) is proprietary information > for the sole use of its > intended recipient. Any unauthorized review, use or distribution by anyone > other than the intended > recipient is strictly prohibited. If you are not the intended recipient, > please notify the sender by > replying to this email, and then delete this email and any copies of it > immediately. Thank you. > > --------------------------------------------------------------------------- > > > > --0015175cb498ed9222046dc703bd--