I don't really have any idea yet what that request rate would be that would overwhelm a single RS; I assume the CPU overhead to server from cache is pretty small so it'd have to be a very high rate.
I was originally more concerned about the aggregate CPU utilization on the RS caused by both connection management and cache serving, but if we have connection pools per Tomcat server that's less of a concern now. We're looking a serving a eCommerce catalog from HBase and our data access patterns won't be as random as some of the examples I've seen of other production sites using HBase, hence the concern. We'll know more in the next couple of weeks. Brad On Feb 17, 2010, at 11:36 AM, Stack wrote: > On Wed, Feb 17, 2010 at 11:27 AM, Brad McCarty <mcca...@gmail.com> wrote: >>> This is hbase. You don't buy bigger hardware, you just add nodes (smile). >> >> >> Not sure if that was tongue-in-cheek, because adding nodes wouldn't address >> the hot row issue would it?? >> > > Yes. I was trying to do tongue-in-cheek but, yes, you are right, it > would not address the hot row issue (I misread). > > What kind of request rate are you thinking would overwhelm serving a > row from cache? > > St.Ack
