Skip to Content
author's profile photo Former Member
Former Member

Heap areas larger than 200 GB (history)

Hi,

From the HANA mini checks. I see CHID 422 . Heap areas larger than 200 GB (history) <hostname> Pool/RowEngine/MonitorView (1081 GB) none X .

Can anyone suggest how to get Pool/RowEngine/MonitorView reduced to <200. I checked 1999997 but could not find procedure to reduce.

From cmd hdbcons ---> mm bl

mm bl -t Pool/RowEngine/MonitorView

742934976b (1658337 blocks) in use at: Dumping frame 0x00007efcd58ca590:

1: 0x00007efcd58ca590 in ptime::CSColumnMonitor::get_object()+0x0 at CSColumnMonitor.cc:695 (libhdbrskernel.so)

35041984b (382111 blocks) in use at: Dumping frame 0x00007efcd52eb190:

1: 0x00007efcd52eb190 in ltt::string_base >::enlarge_(unsigned long)+0xe0 at char_traits.hpp:208 ( libhdbrskernel.so)

21231232b (88491 blocks) in use at: Dumping frame 0x00007efcd233cc20:

1: 0x00007efcd233cc20 in Diagnose::StatisticsBuffer::create(Diagnose::StatisticsBuffer::Callback&, unsigned long, Diagnose::StatisticsWrapper&, Diagnose::StatisticsData&, ltt::vector const&, bool, unsigned long)+0x9c0 at StatisticsBuffer.cpp:276 ( libhdbbasis.so)

1632960b (8505 blocks) in use at: Dumping frame 0x00007efcd54e17d0:

1: 0x00007efcd54e17d0 in ptime::Catalog::add_monitor_view(ptime::Transaction&, ptime::CreateMonitorViewInfo&)+0x130 at catalog_monitor.cc:130 (libhdbrskernel.so)

288000b (1000 blocks) in use at: Dumping frame 0x00007efcd5760280:

1: 0x00007efcd5760280 in ptime::StatisticsMonitorHandle::createStatisticsMonitorHandles()+0x30 at memory.hpp:1397 (libhdbrskernel.so)

88704b (462 blocks) in use at: Dumping frame 0x00007efcd54e1730:

1: 0x00007efcd54e1730 in ptime::Catalog::add_monitor_view(ptime::Transaction&, ptime::CreateMonitorViewInfo&)+0x90 at catalog_monitor.cc:105 (libhdbrskernel.so)

73464b (462 blocks) in use at: Dumping frame 0x00007efcd551c2c0:

1: 0x00007efcd551c2c0 in ptime::MonitorViewInfo::createFieldInfoArray()+0x10 at monitorviewinfo.cc:27 (libhdbrskernel.so)

52224b (5 blocks) in use at: Dumping frame 0x00007efcd52eb19d:

1: 0x00007efcd52eb19d in ltt::string_base >::enlarge_(unsigned long)+0xe9 at memory.hpp:845 ( libhdbrskernel.so)

1536b (12 blocks) in use at: Dumping frame 0x00007efcd25e9f30:

1: 0x00007efcd25e9f30 in MemoryManager::PoolAllocator::createSubAllocator(char const*, ltt::hana_component const&)+0x50 at handle_ref.hpp:479 (libhdbbasis.so)

288b (1 block) in use at: Dumping frame 0x00007efcd7c5ae30:

1: 0x00007efcd7c5ae30 in init_StreamingServicesHandle::init_StreamingServicesHandle()+0x10 at memory.hpp:1397 (libhdbrskernel.so)

Regards,

DK

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    Posted on Aug 10, 2016 at 01:09 PM

    What revision are you running?

    The only way to release this memory is a restart of the indexserver.

    There is a known issue to SAP that is fixed as of Revision 112.05. No work around is available (except for restarting the indexserver).

    If your revision is higher than 112.05 then open an incident and send me the incident number.

    This may of interest too 2343177 - Memory leak in Pool/RowEngine/MonitorView in scale-out system

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 10, 2016 at 07:37 PM

    Please close off

    Thanks

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 10, 2016 at 01:18 PM

    Hi Dinesh,

    Check if note 2112732 - Pool/RowEngine/MonitorView allocates large amount of memory helps or not.

    Regards,

    Ning

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.