When I use the MOT feature of the openGauss database, the numa_node node is full and is not released for a long time. How can I manually release it? Is there any quick method?
When I use the MOT feature of the openGauss database，how can I manually release the numa_node node?
74 Views Asked by Sarah At
1
There are 1 best solutions below
Related Questions in OPEN-GAUSS
- Consult the mot problem of the openGauss database
- When I use the MOT feature of the openGauss database，how can I manually release the numa_node node?
- does openGauss MOT support cross-engine query now?
- The problem of importing MOT table using gs_restore in openGauss database
- Global memory problems when the MOT feature is used in the openGauss database
- What should I do if the error message “unknow:26000” is displayed when GSQL is used to connect to the database?
- What should I do if the following error is reported when I use SQLDriverConnect to connect to the openGaus database?
- About mysql compatibility in openGauss 3.1.0 ？
- Is openGauss 3.1.1 fully compatible with PosgreSQL 14.2 in SQL syntax?
- What's the relationship between openGauss and PG?
- Failed to compile opengauss
- When the synchronous_commit parameter is used in standalone and primary/standby modes, are the meanings of the values local and on different?
- Specifying the order of join inopenGauss
- Does openGauss MOT purely in-memory table?
- How to install openGauss on a Python 3.7 environment
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
The question is interesting and though there is a short answer it requires an explanation.
Short answer:
VACUUM FULL [MOT_table1];This is useful only when MOT table sizes are significantly reduced (possibly periodically) and are not expected to grow to their original size in the near future.Explanation: openGauss MOT has a highly optimized memory management, welcome to read here about its NUMA awareness allocation and affinity and about MOT Memory Planning.
Firstly, to facilitate quick operation and make efficient use of NUMA nodes, MOT allocates a designated memory pool for rows per table and for nodes per index. Each such pool is composed of 2 MB chucks. A designated API allocates these chunks from a local NUMA node, from pages coming from all nodes or in a round-robin fashion, where each chunk is allocated on the next node. By default, pools of shared data are allocated in a round robin fashion in order to balance access, while not splitting rows between different NUMA nodes. However, thread private memory is allocated from a local node. It must also be verified that a thread always operates in the same NUMA node.
Secondly, MOT design expects data growth, thus once a memory chunk was added to the memory pool and used (insert of data) then at delete of rows will mark internally memory sections as the free and ready for re-use, and are not released back to the operating system.
A manually activated VACUUM command can optimize rows distribution within and across memory chunks, move them into densely populated, and free the remaining memory chunks to the OS.