Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 15325 invoked from network); 5 Jan 2011 15:50:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Jan 2011 15:50:17 -0000 Received: (qmail 22212 invoked by uid 500); 5 Jan 2011 15:50:16 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 22024 invoked by uid 500); 5 Jan 2011 15:50:16 -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 22015 invoked by uid 99); 5 Jan 2011 15:50:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jan 2011 15:50:15 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of alarmnummer@gmail.com designates 74.125.83.41 as permitted sender) Received: from [74.125.83.41] (HELO mail-gw0-f41.google.com) (74.125.83.41) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jan 2011 15:50:09 +0000 Received: by gwj22 with SMTP id 22so7237261gwj.14 for ; Wed, 05 Jan 2011 07:49:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=Z7e0CTwCFZ1wBr1W0dhEC71LwlgDmosJUsynQyrORuM=; b=QXFTeLAVcUMQih7lwrkEiM7qWDgUXnxs3RfI2XQ3kuD0lkWwTSdYvhyukzctcF+mE4 omeDVfP/JAkmqyrvMYfoyp8qXSXyAQgNX2NnWOiV79fvrrJqJCBIX/8GEBdDDOWeQhh2 DX/DjaWjOaS6sRXleuXVBGqKzAqUYhFxuhH9E= 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=n1c/nGgkVhoM5eTOBJFJWdHsgjH10ESmPwbUjt/VHndLj8Rw5jcRsLBdtAIFR4dMKL 6OJrOMvziLHHWG7tURAzo2t43zjzX1Yv0e0CRZ7nwINZnO70j1pCTJJ2W9yweYrETLs0 PSN6Vg3dbUnUcY2Uvwg2krH0vCWwYcmOZoT3c= MIME-Version: 1.0 Received: by 10.100.110.7 with SMTP id i7mr13577264anc.16.1294242588384; Wed, 05 Jan 2011 07:49:48 -0800 (PST) Received: by 10.101.129.34 with HTTP; Wed, 5 Jan 2011 07:49:48 -0800 (PST) In-Reply-To: References: <291E2190-F1B3-43BF-9EA0-64D8C3F43507@xebia.com> Date: Wed, 5 Jan 2011 16:49:48 +0100 Message-ID: Subject: Re: Using HBase in combination with HDFS directly From: Peter Veentjer To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=0016e644c4d8bbdd9604991b552b X-Virus-Checked: Checked by ClamAV on apache.org --0016e644c4d8bbdd9604991b552b Content-Type: text/plain; charset=ISO-8859-1 I also want to see if an STM like Multiverse can be aligned with NoSQL solutions like HBase. But to do that, I first need to get more hands on experience with NoSQL solutions. On Wed, Jan 5, 2011 at 4:34 PM, Peter Veentjer wrote: > > > On Wed, Jan 5, 2011 at 4:03 PM, Friso van Vollenhoven < > fvanvollenhoven@xebia.com> wrote: > >> Hi Peter, >> >> Do you mean you want to use the HDFS that HBase relies on for other things >> and not just exclusively HBase? That should be just fine. We do it all the >> time. >> >> > Ok thanks. > > > >> Are you worried about putting to much load on it? > > > For the POC it won't matter that much. I can get my stuff up and running. > > >> I guess that depends on the type of work load that you have and what you >> do with it. But generally I think it is nice to have all nodes be the same >> (so all workers are datanode and region server), such that you don't have to >> scale out them separately. >> > > >>Peter, are you based in The Netherlands by any chance? There is a NoSQL > meetup group in NL (http://www.meetup.com/nosql-nl/) with >>meetups every > now and then. Next one is at January 24 and is all about HBase. We're doing > a on the spot install on a number of present >>laptops to create a temporary > cluster and play around with it. I have been working with Hadoop and HBase > for the past couple of months, so if >>you care to come by, I'd be happy to > share some experiences. > > Yet I live in Holland. I'm a former Xebia employee :) I think I'll visit > one of the nosql meetups. > > We are building a kind of application server where instead of providing > services like JMS, Servlet, EJB's etc we are providing services for secured > document storage, message exchange, semantic analysis of documents etc. It > is all based on GigaSpaces but I have the impression (after working more > than a year with it) that is is very time consuming to get right. Apart from > all the correctness issues (and there where/are many.. based on bad usage of > GigaSpaces and architectural choices) there are also some > performance/scalability issues that need solving. > > So I decided to rewrite the main use cases using HBase. I had most of the > functionality up and running in a few days and most of the 'bad > architectural choices' we are going to remove in the next 6 months are not > there from the beginning (e.g. using streams instead of byte arrays for > document processing.. how stupid can you be). It also was a nice exercise to > play with HBase and less consistent solutions. > > I normally work on realizing very high consistency for Multiverse: > > http://multiverse.codehaus.org > > So I want to have some hands on experience with using less consistent > solutions. > > >> >> Friso >> >> >> >> On 5 jan 2011, at 14:41, Peter Veentjer wrote: >> >> > Hi Guys, >> > >> > I'm currently writing a POC based on hbase and I spend more time on >> writing >> > a ui than on writing the hbase functionality. So I'm very excited about >> > exploring HBase further and doing some serious performance and >> scalability >> > tests and see if we can use it as core technology instead of the >> > time/resource intensive Gigaspaces. >> > >> > My question: >> > >> > I'm currently using HBase and I also want to use the HDFS directly to >> store >> > files. If the HBase server(s) is installed, can I directly access the >> HDFS >> > of these servers or is it better to set up a seperate Hadoop server for >> > running HDFS. >> >> > --0016e644c4d8bbdd9604991b552b--