Another way can be to extend the existing load balancer and to add the
logic to spread your table only on the servers you want?
2013/2/4, T Vinod Gupta <[EMAIL PROTECTED]>:
> in a distributed hbase setup with multiple (just a few) tables, is it
> possible to assign a table to a specific node or set of nodes (region
> the scenario im trying to address is that - i have a process that accesses
> only 1 table and that process has very high requirements for throughput and
> SLAs to meet. So if i want to isolate it from the other tables that may
> have heavy transactions (or bursts of transactions) happening, then whats
> the best approach?
> one way of accomplishing is to have a separate hbase setup for this
> application. but then it means managing different installations and
> servicing them. also, the application uses other tables to load data into
> this key table that is supporting api request traffic. so the app will have
> to talk to 2 different zoo keepers. not the ideal solution it seems.