Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of dean.hiller@broadridge.com
 designates 64.18.2.171 as permitted sender)
From: "Hiller, Dean  x66079" <dean.hiller@broadridge.com>
To: "Hiller, Dean  x66079" <dean.hiller@broadridge.com>,
        "user@hbase.apache.org" <user@hbase.apache.org>
CC: "hbase-user@hadoop.apache.org" <hbase-user@hadoop.apache.org>
Date: Thu, 9 Jun 2011 12:20:04 -0400
Subject: RE: in-memory data grid vs. ehcache + hbase
Thread-Topic: in-memory data grid vs. ehcache + hbase
Thread-Index: AcwmBhc+/UIUawnLRzSWuVZ6mEshjwAujN4wAAAaF+A=
Message-ID: 
 <08230D4C8E666D479F6DE495A7684DCD0AABCFB0@JSCPCWEXMAA1.bsg.ad.adp.com>
References: <Acwl9UG+6ygd7E/PTVm9OcrMAKosGQ==>
	<08230D4C8E666D479F6DE495A7684DCD0AABCB1B@JSCPCWEXMAA1.bsg.ad.adp.com>
 <BANLkTin+wsWuwE0n=TfG9tQqd0UbDekqAg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

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 o=
ur performance increase would be around 100 times in this case....we are cu=
rrently using something other than hbase and when we change to this type of=
 design it flies.

Thanks,
Dean

-----Original Message-----
From: Hiller, Dean x66079=20
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 wh=
ere it would work like this

1. write using hbase client into the grid which came from some web update(w=
hich is VERY rare occurrence as this is admin stuff)
2. write something out to all nodes telling it to evict the stale entry fro=
m 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 an=
other 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 wit=
h 1,000,000 rows. =A0We have found out that having a copy/cache on each nod=
e is EXTREMELY fast for our batch processing since these copies of data are=
 local AND in-memory. =A0The issue I am struggling with is the best way to =
evict stale entries from the cache since these entries are rarely updated i=
n our system, but we still need to evict them from all nodes. =A0Anyone els=
e 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 add=
ressee and
may contain information that is privileged and confidential. If the reade=
r of the =

message is not the intended recipient or an authorized representative of =
the
intended recipient, you are hereby notified that any dissemination of thi=
s
communication is strictly prohibited. If you have received this communica=
tion in
error, please notify us immediately by e-mail and delete the message and =
any
attachments from your system.
=0D