box/memtx: Allow to skip tuple memory from coredump
In case if there are huge amount of tuples the whole memory goes to coredump file even if we don't need it for problem investigation. In result coredump may blow up to gigabytes in size. Lets allow to exclude this memory from dumping via box.cfg::strip_core boolean parameter. Note that the tuple's arena is used not only for tuples themselves but for memtx->index_extent_pool and memtx->iterator_pool as well, so they are affected too. Fixes #3509 @TarantoolBot document Title: Document box.cfg.strip_core When Tarantool runs under a heavy load the memory allocated for tuples may be very huge in size and to eliminate this memory from being present in `coredump` file the `box.cfg.strip_core` parameter should be set to `true`. The default value is `false`.
Showing
- src/box/box.cc 1 addition, 0 deletionssrc/box/box.cc
- src/box/lua/load_cfg.lua 2 additions, 0 deletionssrc/box/lua/load_cfg.lua
- src/box/memtx_engine.c 2 additions, 2 deletionssrc/box/memtx_engine.c
- src/box/memtx_engine.h 6 additions, 3 deletionssrc/box/memtx_engine.h
- src/box/tuple.c 12 additions, 3 deletionssrc/box/tuple.c
- src/box/tuple.h 1 addition, 1 deletionsrc/box/tuple.h
- src/box/vy_mem.c 1 addition, 1 deletionsrc/box/vy_mem.c
- src/lib/core/memory.c 1 addition, 1 deletionsrc/lib/core/memory.c
- src/lib/small 1 addition, 1 deletionsrc/lib/small
- src/main.cc 12 additions, 0 deletionssrc/main.cc
- test/box/admin.result 2 additions, 0 deletionstest/box/admin.result
- test/box/cfg.result 4 additions, 0 deletionstest/box/cfg.result
Loading
Please register or sign in to comment