On Fri, Oct 19, 2012 at 5:22 PM, Amandeep Khurana wrote:
> Answers inline
>
> On Fri, Oct 19, 2012 at 4:31 PM, Dave Latham wrote:
>
>> I need to scale an internal service / datastore that is currently hosted on
>> an HBase cluster and wanted to ask for advice from anyone out there who may
>> have
> Here are a few of my thoughts:
>
> If possible, you might want to localize your data to a few regions if you can
> and then may be have exclusive access to those regions. This way, external
> load will not impact you. I have heard that write penalty of SSDs is quite
> high. But I think, they
What Amandeep said, and also:
You said your working set is randomly distributed but, if frequent
invalidation isn't a concern and read accesses are still clustered
temporally, an in-memory cache out in front of the cluster would smooth
over periods when the disks are busy servicing MR workload or
Answers inline
On Fri, Oct 19, 2012 at 4:31 PM, Dave Latham wrote:
> I need to scale an internal service / datastore that is currently hosted on
> an HBase cluster and wanted to ask for advice from anyone out there who may
> have some to share. The service does simple key value lookups on 20 by
Here are a few of my thoughts:
If possible, you might want to localize your data to a few regions if you can
and then may be have exclusive access to those regions. This way, external load
will not impact you. I have heard that write penalty of SSDs is quite high.
But I think, they will still
