hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stack <st...@duboce.net>
Subject Re: commit semantics
Date Tue, 12 Jan 2010 18:51:32 GMT
On Tue, Jan 12, 2010 at 10:14 AM, Dhruba Borthakur <dhruba@gmail.com> wrote:

> Hi stack,
>
> I was meaning "what if the application inserted the same record into two
> Hbase instances"? Of course, now the onus is on the appl to keep both of
> them in sync and recover from any inconsistencies between them.
>
>
Ok.  Like your  "Overlapping Clusters for HA" from
http://www.borthakur.com/ftp/hdfs_high_availability.pdf?

I'm not sure how the application could return after writing one cluster
without waiting on the second to complete as you suggest above.  It could
write in parallel but the second thread might not complete for myriad
reasons.  What then?  And as you say, reading, the client would have to make
reconciliation.

Isn't there already a 'scalable database' that gives you this headache for
free without your having to do work on your part (smile)?

Do you think there a problem syncing on every write (with some batching of
writes happening when high-concurrency) or, if that too slow for your needs,
adding the holding of clients until sync happens as joydeep suggests?  Will
that be sufficient data integrity-wise?

St.Ack

Thanks,
St.Ack

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