Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: 关于tmp-storage-path产生的临时磁盘占用不会自动释放问题
|
username: TiDBer_菜鸟
In the current version TIDBv4.09, when the memory usage of a single SQL statement exceeds the mem-quota-query limit, some operators temporarily occupying disk storage do not automatically release it. I would like to ask how you experts handle this.
The default value of server-memory-quota is 0, which means there is no memory limit.
Increase mem-quota-query and set oom-use-tmp-storage to FALSE
mem-quota-query
The maximum memory threshold that a single SQL statement can use, in bytes.
Default value: 1073741824
Requests exceeding this value will be handled by the behavior defined by oom-action.
This value serves as the initial value for the system variable tidb_mem_quota_query 21.
oom-use-tmp-storage
Sets whether to enable temporary disk for certain operators when the memory usage of a single SQL statement exceeds the mem-quota-query limit.
Default value: true
Currently, it is still impossible to assess the impact of the upgrade on the business 
Currently, the memory pressure is already quite high. Will increasing the memory threshold affect other normal queries? The company also does not plan to allocate funds for expansion at the moment.
The performance improvement was significant when I upgraded from 4.0.9 to 5.4 last year.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: 
|
username: 
|
username: 
|
username: 
|
username: