hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4329) Use NextGen Hadoop to deploy HBase
Date Sun, 04 Sep 2011 23:18:09 GMT

    [ https://issues.apache.org/jira/browse/HBASE-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096961#comment-13096961
] 

stack commented on HBASE-4329:
------------------------------

bq. Currently (circa 2011), with due respect, it's not practical to run shared, multi-tenant
HBase clusters on the largest Hadoop installs (of 4000+ nodes).

Why you say that? (I don't disagree but a list of why's would help figure what the fit criteria
for closing this issue are).

Up to now, in our ignorance, we've been thinking a fat hbase install w/ multitenancy enabled
via hbase security acls.  Regards resources consumed by the running hbase, there is an interesting
contribution over in HBASE-4120 that is provocative but I'm thinking needs a bit of work before
it'd be committed.  Meantime, where I work, mapreduce is the problem (smile).  We're messing
with cgroup containing mapreduce so it doesn't steal resources from hdfs (and hbase).

You want us to get into the nextgen mr container because then there is one place to go to
do accounting?  I need to do some background reading over on mapreduce-279 to see what we're
missing.

Good on you Arun.

> Use NextGen Hadoop to deploy HBase
> ----------------------------------
>
>                 Key: HBASE-4329
>                 URL: https://issues.apache.org/jira/browse/HBASE-4329
>             Project: HBase
>          Issue Type: Brainstorming
>            Reporter: Arun C Murthy
>
> Currently (circa 2011), with due respect, it's not practical to run shared, multi-tenant
HBase clusters on the largest Hadoop installs (of 4000+ nodes).
> As an interim, I'd like to brainstorm using NextGen Hadoop (MAPREDUCE-279) to deploy
HBase for focussed sets of applications/users/organizations. Thus, one could deploy a smaller
instance of HBase (100s of nodes) in a large Hadoop cluster and use it for a set of applications.
> The other advantage is that the resource usage of HBase (master, region-server etc.)
is accounted for in the overall utilization of the cluster and, conceivably, aid in resource
tracking, capacity planning etc.
> ----
> Thoughts?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message