[
https://issues.apache.org/jira/browse/HBASE-13097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14337549#comment-14337549
]
zhangduo commented on HBASE-13097:
----------------------------------
Oh yeah, it is PooledByteBufAllocator.DEFAULT, not
PooledByteBufAllocator.class, sorry...
So the problem is still that we create too many EventLoopGroup which has its
own thread pool that causes too many alive threads?
If you all agree, we can change the title of this issue to "Reduce Connection
and RpcClient creations in unit tests", and create sub tasks to handle tests
one by one?
Thanks. [~jurmous] [~stack]
> Netty PooledByteBufAllocator cause OOM in some unit test
> --------------------------------------------------------
>
> Key: HBASE-13097
> URL: https://issues.apache.org/jira/browse/HBASE-13097
> Project: HBase
> Issue Type: Bug
> Components: IPC/RPC, test
> Affects Versions: 2.0.0, 1.1.0
> Reporter: zhangduo
>
> In some unit tests(such as TestAcidGuarantees) we create multiple Connection
> instance. If we use AsyncRpcClient, then there will be multiple netty
> Bootstrap and every Bootstrap has its own PooledByteBufAllocator.
> I haven't read the code clearly but it uses some threadlocal technics and
> jmap shows io.netty.buffer.PoolThreadCache$MemoryRegionCache$Entry is the
> biggest things on Heap.
> See
> https://builds.apache.org/job/HBase-TRUNK/6168/artifact/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.TestAcidGuarantees-output.txt
> {noformat}
> 2015-02-24 23:50:29,704 WARN [JvmPauseMonitor]
> util.JvmPauseMonitor$Monitor(167): Detected pause in JVM or host machine (eg
> GC): pause of approximately 20133ms
> GC pool 'PS MarkSweep' had collection(s): count=15 time=55525ms
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
