hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bingbing Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17671) HBase Thrift2 OutOfMemory
Date Tue, 21 Feb 2017 03:52:44 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875327#comment-15875327
] 

Bingbing Wang commented on HBASE-17671:
---------------------------------------

The Thrift2 heap dump file is very big (about 4G, and more than 180M even after compression),
so I couldn't upload it.

I have used the MemoryAnalyzer to parse the heap dump, and it showed that many memory are
held by scannerMap and org.apache.thrift.transport.TFramedTransport writeBuffer. Not clearly
why some many writeBuffer is not freed.

Could your guys take a look and give some explanation?

> HBase Thrift2 OutOfMemory
> -------------------------
>
>                 Key: HBASE-17671
>                 URL: https://issues.apache.org/jira/browse/HBASE-17671
>             Project: HBase
>          Issue Type: Bug
>          Components: Thrift
>    Affects Versions: 0.98.6
>         Environment: Product
>            Reporter: Bingbing Wang
>            Priority: Critical
>         Attachments: hbase-site.xml, hbase-thrift2.log, log_gc.log.0.zip
>
>
> We have a HBase Thrift2 server deployed on Windows, basically the physical view looks
like:
> QueryEngine <==> HBase Thrift2 <==> HBase cluster
> Here QueryEngine is a C++ application, and HBase cluster is a about 50-nodes HBase cluster
(CDH 5.3.3, namely Hbase version 0.98.6).
> Our Thrift2 Java options looks like:
> -server -Xms4096m -Xmx4096m -XX:MaxDirectMemorySize=8192m -XX:+HeapDumpOnOutOfMemoryError
-XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:G1HeapRegionSize=4M -XX:InitiatingHeapOccupancyPercent=40
-XX:+PrintAdaptiveSizePolicy -XX:+PrintPromotionFailure -Dhbase.log.dir=d:\vhayu\thrift2\log
-verbose:gc -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -XX:PrintFLSStatistics=1
-Xloggc:log_gc.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=200M
-Dhbase.log.file=hbase-thrift2.log  -Dhbase.home.dir=D:\vhayu\thrift2\hbase0.98 -Dhbase.id.str=root
-Dlog4j.info -Dhbase.root.logger=INFO,DRFA -cp "d:\vhayu\thrift2\hbase0.98\*;d:\vhayu\thrift2\conf"
org.apache.hadoop.hbase.thrift2.ThriftServer -b 127.0.0.1 -f framed start
> The phenomenon of  the issue is that after some time running, Thrift2 sometimes reports
OOM and heap dump file (.hprof) file was generated. The consequence of this will always trigger
high latency form HBase cluster.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message