Thanks, I was aware of the issue with WALs but had not considered bulkload and
archive.
Roberta
-Original Message-
From: Esteban Gutierrez [mailto:este...@cloudera.com]
Sent: Monday, March 13, 2017 10:50 AM
To: user@hbase.apache.org
Subject: Re: HBase namespaces and encryption
Hel
There are different thread pools in the client, and some of the thread
pools depend on how are you constructing connection and table instances.
The first thread pool is the one owned by the connection. If you are using
ConnectionFactory.createConnection() (which you should) then this is the
proper
I think you need to set that property before you make HBaseConfiguration
object. Have you tried that?
On Mon, Mar 13, 2017 at 10:24 AM, Henning Blohm
wrote:
> Unfortunately it doesn't seem to make a difference.
>
> I see that the configuration has hbase.htable.threads.max=1 right before
> settin
Hello Roberta,
I think there are too many caveats of using an encryption zone per
namespace. Specially, bulkloading and the archive will fail; another
problem is about the security guarantees that you are offering to your
tenants, the WALs and oldWALs directories will have to be under the same
enc
Unfortunately it doesn't seem to make a difference.
I see that the configuration has hbase.htable.threads.max=1 right before
setting up the Connection but then I still get hundreds of
hconnection-***
threads. Is that actually Zookeeper?
Thanks,
Henning
On 13.03.2017 17:28, Ted Yu wrote:
Ar
It's that simple...? Thanks so much! Will give it a try right away.
Thanks, Henning
On 13.03.2017 17:28, Ted Yu wrote:
Are you using Java client ?
See the following in HTable :
public static ThreadPoolExecutor getDefaultExecutor(Configuration conf) {
int maxThreads = conf.getInt("hbas
Are you using Java client ?
See the following in HTable :
public static ThreadPoolExecutor getDefaultExecutor(Configuration conf) {
int maxThreads = conf.getInt("hbase.htable.threads.max", Integer.
MAX_VALUE);
FYI
On Mon, Mar 13, 2017 at 9:14 AM, Henning Blohm
wrote:
> Hi,
>
> I am runn
Hi,
I am running an HBase client on a very resource limited machine. In
particular numproc is limited so that I frequently get "Cannot create
native thread" OOMs. I noticed that, in particular in write situations,
the hconnection pool grows into the hundreds of threads - even when at
most wri
Hi
I want to join a Spark RDD with an HBase table. Im familiar with the
different connectors available but couldn't find this functionality.
The idea I have is to first sort the RDD according to a byte[] key [1]
and rdd.mapPartitions so that I each partition contains a unique and
sequentially sor
