hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stack <st...@duboce.net>
Subject Re: Shift entirely to HBase?
Date Fri, 03 Apr 2009 22:19:10 GMT
Oh, you could also set your columns to flush more frequently than default so
edits are presisted more often.
St.Ack

On Sat, Apr 4, 2009 at 12:16 AM, stack <stack@duboce.net> wrote:

> Good.  I'm glad you are doing the evaluations.  My guess is that you'll
> need to wait on 0.20.0 to get the realtime numbers you'll be happy with.
>
> Look through hbase JIRAs for issues on backups.  There are a few.  I think
> Erik Holstad's the most up-to-date.  Check it out (A google summer of code
> project looks like it will concentrate on this particular issue snapshotting
> tables).
>
> St.Ack
>
>
> On Fri, Apr 3, 2009 at 8:19 PM, Vaibhav Puranik <vpuranik@gmail.com>wrote:
>
>> Stack,
>>
>> We are still trying to explore answers to these questions.
>>
>> For example, we are at this moment doing performance testing on hbase to
>> see
>> whether it can be used as a real time database.
>>
>> We haven't finalized the new schema - I am exploring the table based
>> indexes
>> feature to see how it can help us to do "where somecolumn = value" where
>> somecolumn is not the row key. We are still getting used to designing the
>> new way.
>>
>> We certainly cannot afford to loose data. Can you (or anybody) give me
>> pointers for backing up hbase data?
>>
>> Regards,
>> Vaibhav Puranik
>> Gumgum Inc.
>>
>>
>> On Thu, Apr 2, 2009 at 11:37 PM, stack <stack@duboce.net> wrote:
>>
>> > Can you do all queries you do in mysql against hbase?
>> >
>> > Does hbase run fast enough for your needs?
>> >
>> > Can you tolerate lost data (hdfs does not yet have a working flush/sync
>> so
>> > dataloss is possible on machine crash -- hopefully fixed in hadoop
>> 0.21).
>> >
>> > St.Ack
>> >
>> >
>> > On Fri, Apr 3, 2009 at 1:16 AM, Vaibhav Puranik <vpuranik@gmail.com>
>> > wrote:
>> >
>> > > Hi,
>> > >
>> > > In our system we have some fast growing tables and some slow growing
>> > tables
>> > > (as in every system).
>> > > Some slow growing tables only have 100s of rows and they grow at a
>> very
>> > > slow
>> > > rate - e.g. users in a small organization.
>> > >
>> > > We are thinking about ditching mysql and adopting Hbase. Is it advised
>> to
>> > > ditch mysql altogether and shift to HBase or do you recommend just
>> > shifting
>> > > fast growing tables to Hbase?
>> > >
>> > > What are other people doing?
>> > >
>> > > Regards,
>> > > Vaibahv
>> > >
>> >
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message