Fix OOM bug that SegmentBitset allocate more than the 2M size
This commit is contained in:
@ -824,7 +824,10 @@ int ObTenantSqlMemoryManager::get_max_work_area_size(int64_t& max_wa_memory_size
|
||||
if (OB_FAIL(ObResourceMgr::get_instance().get_tenant_resource_mgr(tenant_id_, resource_handle))) {
|
||||
ret = OB_SUCCESS;
|
||||
} else {
|
||||
max_tenant_memory_size += resource_handle.get_memory_mgr()->get_cache_hold();
|
||||
// TODO: kvcache大概可以淘汰多少内存,目前没有数据,后续寒晖他们会提供接口
|
||||
// bug34818894 https://work.aone.alibaba-inc.com/issue/34818894
|
||||
// 这里暂时写一个默认比例
|
||||
max_tenant_memory_size += resource_handle.get_memory_mgr()->get_cache_hold() * 0.05;
|
||||
}
|
||||
}
|
||||
int64_t remain_memory_size =
|
||||
|
||||
Reference in New Issue
Block a user