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

MVCC activated and causing memory leak (OOM) despite no mvccEnabled caches

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.7.5
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Ignite Flags:
      Docs Required, Release Notes Required

      Description

      We have a critical memory leak where mvccCoordinator is still selected and mvcc is still 'activated' despite having no mvccEnabled caches, this is causing constant OOM crashes and issues on both server and client nodes.

      All client CacheAtomicityModes are of type ATOMIC, and for server config persistence is false, TCPDiscoverySpi used and PeerClassLoadingEnabled=true.

      There are two server JVM instances on two separate nodes. One of the servers consistently get an OOM error, as well as all clients, due to the same recoveryBallotBoxes HashMap constantly increasing in size and unable to be Garbage Collected.

      Attached is Eclipse Memory Analyzer Tool screenshot on the heap dump close to one of the server JVM OOM crashes. The same heap analysis result is apparent for all clients as well.

        Attachments

        1. MATheap.jpg
          118 kB
          Ming Vuong

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mingvuong Ming Vuong
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: