hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stack <st...@duboce.net>
Subject Re: in-memory data grid vs. ehcache + hbase
Date Thu, 09 Jun 2011 16:39:07 GMT
I don't know of a generic soln to the prob. you describe.  Sounds like
you have hacked up something for your purposes only the local cache is
read-only?  Can't you change your inserts so they update both hbase
and push out to local cache?


On Thu, Jun 9, 2011 at 9:20 AM, Hiller, Dean  x66079
<dean.hiller@broadridge.com> wrote:
> Oh, and I was hoping something like this kind of framework using the hbase slaves file
was already existence...hard to believe it would not be since our performance increase would
be around 100 times in this case....we are currently using something other than hbase and
when we change to this type of design it flies.
> Thanks,
> Dean
> -----Original Message-----
> From: Hiller, Dean x66079
> Sent: Thursday, June 09, 2011 10:16 AM
> To: user@hbase.apache.org
> Cc: hbase-user@hadoop.apache.org
> Subject: RE: in-memory data grid vs. ehcache + hbase
> Well, I was hoping there is something with ehcache or some kind of cache where it would
work like this
> 1. write using hbase client into the grid which came from some web update(which is VERY
rare occurrence as this is admin stuff)
> 2. write something out to all nodes telling it to evict the stale entry from the cache
> Then on the next read on any node, it gets the new data.  It is okay if one node gets
a different value during the transition to the new value than another node and that it becomes
eventually consistent.
> Thanks,
> Dean
> -----Original Message-----
> From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of Stack
> Sent: Wednesday, June 08, 2011 12:01 PM
> To: user@hbase.apache.org
> Cc: hbase-user@hadoop.apache.org
> Subject: Re: in-memory data grid vs. ehcache + hbase
> On Wed, Jun 8, 2011 at 9:00 AM, Hiller, Dean  x66079
> <dean.hiller@broadridge.com> wrote:
>> We have certain tables with under 10 rows, one under 200 rows and one with 1,000,000
rows.  We have found out that having a copy/cache on each node is EXTREMELY fast for our
batch processing since these copies of data are local AND in-memory.  The issue I am struggling
with is the best way to evict stale entries from the cache since these entries are rarely
updated in our system, but we still need to evict them from all nodes.  Anyone else struggling
with this problem?
> You are caching hbase content in ehcache and you are trying to figure
> how to have ehcache have a true reflection of hbase content?
> St.Ack
> This message and any attachments are intended only for the use of the addressee and
> may contain information that is privileged and confidential. If the reader of the
> message is not the intended recipient or an authorized representative of the
> intended recipient, you are hereby notified that any dissemination of this
> communication is strictly prohibited. If you have received this communication in
> error, please notify us immediately by e-mail and delete the message and any
> attachments from your system.

View raw message