You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by Serega Sheypak <se...@gmail.com> on 2014/09/02 22:15:40 UTC

HBase java.util.concurrent.RejectedExecutionException

Hi, I'm using HBase CDH 4.7 and do get this exception during integration
tests:

ava.util.concurrent.RejectedExecutionException: null
at
java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1774)
 at
java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:768)
at
java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:656)
 at
java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:92)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1697)
 at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1560)
at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:1031)
 at org.apache.hadoop.hbase.client.HTable.put(HTable.java:865)
at
org.apache.hadoop.hbase.client.HTablePool$PooledHTable.put(HTablePool.java:395)

I don't use put operation in production, so I never get nay problems. I use
put operation during test to populate table with data.
This exception happens from time to time. What do I do wrong?

Re: HBase java.util.concurrent.RejectedExecutionException

Posted by Andrey Stepachev <oc...@gmail.com>.
Hello Serega.

Looks like closed HTable.pool.
Thats could happen if HTable is closed while operation in progress (put in
your case). Check that HTable is not closed too early or concurrently with
put operation.

On Wed, Sep 3, 2014 at 12:15 AM, Serega Sheypak <se...@gmail.com>
wrote:

> Hi, I'm using HBase CDH 4.7 and do get this exception during integration
> tests:
>
> ava.util.concurrent.RejectedExecutionException: null
> at
>
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1774)
>  at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:768)
> at
>
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:656)
>  at
>
> java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:92)
> at
>
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1697)
>  at
>
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1560)
> at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:1031)
>  at org.apache.hadoop.hbase.client.HTable.put(HTable.java:865)
> at
>
> org.apache.hadoop.hbase.client.HTablePool$PooledHTable.put(HTablePool.java:395)
>
> I don't use put operation in production, so I never get nay problems. I use
> put operation during test to populate table with data.
> This exception happens from time to time. What do I do wrong?
>



-- 
Andrey.