SAP Knowledge Base Article - Preview

3637750 - Pool/Statistics/Allocators/CoreStripedSubStats continuous memory growth

Symptom

  • Continuous growth of CoreStripedSubStats memory allocator in SAP HANA DB.
  • The issue persists until the HANA database is restarted.
  • No significant changes in system parameters or updates to components were observed.
  • You ran the command below on the host and for the service that suffers from the high Pool/Statistics size to display the top contributors in the first place using the blocklist option of hdbcons (SAP Note 2222218):

    hdbcons 'mm bl -t Pool/Statistics/Allocators/CoreStripedSubStats'

  • You notice the blocklist top contributors with ie.

    Try to open connection to server process 'hdbindexserver' on system 'SID', instance '##' and tenant 'SID'
    SAP HANA DB Management Server Console (type 'help' to get help for server commands)
    Executable: hdbindexserver (PID: ######)
    Service: indexserver@sid:<port> (DB##: SID)
    [OK]
    --
    ## Start command at:
    7070469896b (107821 blocks incl. 4.11mb (4312840b) meta data) in use at: Dumping saved stack trace 9223512772170134336, 1 frames:
       0: 0x00007fff7e7ab340 in Execution::ContextAllocator::initImplicitStatementMemoryBooking()+0xb0 at Basis/Execution/impl/ContextAllocator.cpp:70 (libhdbbasis.so)

    6213457152b (94752 blocks incl. 3.61mb (3790080b) meta data) in use at: Dumping saved stack trace 9223512772170090048, 1 frames:
       0: 0x00007fff7e7a0640 in Execution::ContextAllocator::forComponent(ltt::allocator&)+0x160 at Basis/Execution/impl/ContextAllocator.cpp:198 (libhdbbasis.so)

    6116732552b (93277 blocks incl. 3.55mb (3731080b) meta data) in use at: Dumping saved stack trace 9223512772170132420, 1 frames:
       0: 0x00007fff7e7aabc4 in Execution::ContextAllocator::ContextAllocator(ltt::allocator&, char const*, char const*)+0x64 at Basis/Execution/impl/ContextAllocator.cpp:32 (libhdbbasis.so)

    31148600b (475 blocks incl. 18.55kb (19000b) meta data) in use at: Dumping saved stack trace 9223512772718750056, 1 frames:
       0: 0x00007fff9f2de968 in Executor::X2::createInstanceAllocatorSecure()+0x78 at executor/X2.cpp:1551 (libhdbexecutor.so)

    28591136b (436 blocks incl. 17.03kb (17440b) meta data) in use at: Dumping saved stack trace 9223512772082305560, 1 frames:
       0: 0x00007fff793e8a18 in ljit::llang::OwnedOptionalSubAllocator::OwnedOptionalSubAllocator(ltt::allocator&, char const*)+0xd8 at llvm/impl/ljit_memoryrules_impl.inc:839 (libhdbljitbase.so)

    21181048b (323 blocks incl. 12.61kb (12920b) meta data) in use at: Dumping saved stack trace 9223512772083770928, 1 frames:
       0: 0x00007fff7954e630 in ljit::llang::LlangCompileImpl::createJitCodeHandle(ljit::llang::LlangContext*, ljit::llang::LlangProgramId const&, ltt::basic_string<char, ltt::char_traits<char>, 39ul> const&, ltt::unique_p          tr<ljit::llang::LlangCodeAnalysisInfo, ltt::with_alloc_t, ltt::default_delete<ljit::llang::LlangCodeAnalysisInfo>, ltt::integral_constant<bool, false> >&, ljit::llang::LlangCompileMessages&, ljit::jit::OptSettings cons          t&, ljit::llang::CompileInfo*, long&, unsigned long&, ltt::set<ltt::smartptr_handle<ljit::llang::ILlangLib>, ltt::less<ltt::smartptr_handle<ljit::llang::ILlangLib> >, ltt::rb_tree_balancier>&)+0x260 at llvm/impl/ljit_m          emoryrules_impl.inc:814 (libhdbljitbase.so)

    16719920b (298570 blocks incl. 6.83mb (7165680b) meta data) in use at: Dumping saved stack trace 9223512772174494232, 1 frames:
       0: 0x00007fff7ebd3a18 in MemoryManager::StripedAllocator::allocateStriped(void*)+0x1d8 at ltt/memory.hpp:1832 (libhdbbasis.so)

    16394000b (250 blocks incl. 9.76kb (10000b) meta data) in use at: Dumping saved stack trace 9223512772174203424, 1 frames:
       0: 0x00007fff7eb8ca20 in MemoryManager::PoolAllocator::createCompositeAllocator(char const*, ltt::allocator&, ltt::striping_mode)+0xb0 at Basis/MemoryManager/impl/mmPoolAllocator.cpp:1551 (libhdbbasis.so)

    14623448b (223 blocks incl. 8.71kb (8920b) meta data) in use at: Dumping saved stack trace 9223512772173671796, 1 frames:
       0: 0x00007fff7eb0ad74 in MemoryManager::AllocatorMapBase::getOrCreateAllocatorNameMapEntry(char const*)+0x254 at Basis/MemoryManager/impl/mmMallocProxy.cpp:782 (libhdbbasis.so)

    5246080b (80 blocks incl. 3.12kb (3200b) meta data) in use at: Dumping saved stack trace 9223512772944552428, 1 frames:
       0: 0x00007fffaca361ec in Utils.cpp.0fc39f63+0x123 at ims_search_api/Delta/Replay.cpp:2003 (libhdbdeltalog.so)

    Top 20 allocators:
    Pool/Statistics/Allocators/CoreStripedSubStats: 18.24gb (19594237992b) (597117 blocks incl. 18.22mb (19107560b) meta data)
    [OK]


Read more...

Environment

SAP HANA DB 2.0

SAP HANA 2 JDBC client:

    • Versions >= 2.3.38 (SPS03)
    • or higher

Product

SAP S/4HANA all versions

Keywords

corestripedsubstats, sap hana memory, memory allocator growth, m_context_memory, m_prepared_statements, dbs/hdb/stmt_cache_size, composite_statistics_striping, numa, statistics_type, memory management, hana database restart, memory optimization, sap hana troubleshooting. , KBA , HAN-DB-ENG , SAP HANA DB Engines , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.