Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-8469

Non-heap memory leak for calling cluster activation multi times

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.7
    • persistence
    • None

    Description

      Calling multiple time cluster (with enabled persistence and started client nodes) activation ig3CB.cluster().active(true); leads to non-heap memory leak.

      Line org/apache/ignite/internal/pagemem/impl/PageMemoryNoStoreImpl.java:234 looks suspicious because of in case method org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl#start callled multi times (e.g. activate(true) called multi times) we lost info about allocated regions.

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. IGNITE-6538 Ignite Activate/Deactivate Cluster suite: After tests validation improvements test became flaky on TC

          • Blocker - Blocks development and/or testing work, production could not run
          • Resolved
          is related to

          Test - A new unit, integration or system test. IGNITE-8085 Flaky failures in Ignite Client Nodes test suite: Remote node could not start.

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link GitHub Pull Request #3986

          Web Link IgniteTests24Java8_RunAll

          Web Link IGNT-CR-608

          Activity

            People

              mmuzaf Maxim Muzafarov
              mmuzaf Maxim Muzafarov
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: