recommended use for hbase htable and cached hbase configuration

RE: HBase Client Concerns

Many thanks again. I think I'll go initially with cached HBaseConfiguration and one new HTable instance per request thread and accept the resulting slowness overhead per request. When the HTablePool pause/retry param issue is resolved, I can switch to that. To workaround the problem of restarting the client app when the HBase servers are restarted, I can then maybe wrap HTablePool into a class which essentially clears the pool cache [forcing instantiating a new HTable] when any of the HTablePool.getTable() client calls time out, so the client app need not be restarted... Cheers,