Phoenix查询抛InsufficientMemoryException异常

最新推荐文章于 2025-06-26 20:23:22 发布

原创最新推荐文章于 2025-06-26 20:23:22 发布 · 1.7k 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#phoenix

大数据.hbase 专栏收录该内容

12 篇文章

订阅专栏

本文介绍了一个在使用Phoenix查询大规模数据时遇到的异常问题，并详细解释了异常产生的原因及解决方法。通过调整phoenix.query.maxGlobalMemoryPercentage参数，成功解决了因内存分配不足导致的查询失败问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

测试集群中使用Phoenix进行数据查询抛出如下异常：

org.apache.phoenix.exception.PhoenixIOException: org.apache.hadoop.hbase.DoNotRetryIOException: C_PICRECORD,,1463484729784.fccf0ba342b4fe6660edb4081ac498ad.: Requested memory of 142000000 bytes could not be allocated from remaining memory of 710007810 bytes from global pool of 781752729 bytes after waiting for 10000ms.
    at org.apache.phoenix.util.ServerUtil.createIOException(ServerUtil.java:84)
    at org.apache.phoenix.util.ServerUtil.throwIOException(ServerUtil.java:52)
    at org.apache.phoenix.coprocessor.BaseScannerRegionObserver.postScannerOpen(BaseScannerRegionObserver.java:205)
    at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$52.call(RegionCoprocessorHost.java:1308)
    at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$RegionOperation.call(RegionCoprocessorHost.java:1663)
    at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperation(RegionCoprocessorHost.java:1738)
    at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperationWithResult(RegionCoprocessorHost.java:1702)
    at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.postScannerOpen(RegionCoprocessorHost.java:1303)
    at org.apache.hadoop.hbase.regionserver.RSRpcServices.scan(RSRpcServices.java:2119)
    at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:31443)
    at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2035)
    at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:107)
    at org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:130)
    at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:107)
    at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.phoenix.memory.InsufficientMemoryException: Requested memory of 142000000 bytes could not be allocated from remaining memory of 710007810 bytes from global pool of 781752729 bytes after waiting for 10000ms.
    at org.apache.phoenix.memory.GlobalMemoryManager.allocateBytes(GlobalMemoryManager.java:78)
    at org.apache.phoenix.memory.GlobalMemoryManager.allocate(GlobalMemoryManager.java:97)
    at org.apache.phoenix.memory.GlobalMemoryManager.allocate(GlobalMemoryManager.java:103)
    at org.apache.phoenix.coprocessor.ScanRegionObserver.getTopNScanner(ScanRegionObserver.java:233)
    at org.apache.phoenix.coprocessor.ScanRegionObserver.doPostScannerOpen(ScanRegionObserver.java:220)
    at org.apache.phoenix.coprocessor.BaseScannerRegionObserver.postScannerOpen(BaseScannerRegionObserver.java:178)
    ... 12 more
;

数据量千万级别(列数为44)，构建了二级索引表，确保查询能够走二级索引表，查询语句为：

SELECT
    ID,
    WAY_NUM,
    CAR_NUM,
    ORG_NAME,
    ORG_ID,
    CAR_SPEED,
    CAR_NUM_TYPE,
    CAR_NUM_COLOR,
    CAR_TYPE,
    CAR_COLOR,
    CAR_LOGO_TYPE,
    LONGITUDE,
    LATITUDE,
    CAR_IMG_URL,
    CAP_DATE,
    GROUPID,
    DEV_CHN_NAME
FROM
    C_PICRECORD
WHERE
    CAP_DATE >= '2016-05-05 11:14:40'
AND CAP_DATE <= '2016-05-12 11:14:40'
AND CAR_NUM = '粤VFX350'
AND CAP_TYPE=0
ORDER BY CAP_DATE ASC
LIMIT 100000

报错原因为使用了ORDER BY。

google论坛显示如下解决方案：
https://groups.google.com/forum/#!topic/phoenix-hbase-user/KEiDCLVXf6k

将 phoenix.query.maxGlobalMemoryPercentage 调整为40%

<property>
    <name>phoenix.query.maxGlobalMemoryPercentage</name>
    <value>40</value>
</property>

【注意】 必须在hbase集群的regionserver hbase-site.xml里面配置该项并重启hbase集群

经过调整后暂时没出现这个异常。