Uploaded image for project: 'InsightEdge Platform'
  1. GS-12946

Loop of restarts of PU instance in same container cause memory leak

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 12.3
    • Labels:
      None
    • Platform:
      All
    • SalesForce Case ID:
      10618,11037
    • Acceptance Test:
      No acceptance test required
    • Sprint:

      Description

      steps to reproduce:
      1.restart of backup due to memory shortage on same container
      -----
      set gsc with low heap size (128M)
      start default agent
      deploy 1,1 space (max instances per vm 1)
      start benchmark
      wait till getting memory shortage
      see that gsm keep restarting the backup and fails to deploy it due to the shortage.
      wait a while and take heap dump of the container that backup was initially on, and now contains no space instance
      in heap you can see lots of space proxies and several cache managers space engines all are rooted to net.jini.lease.LeaseRenewalManager
      that keeps net.jini.lookup.ServiceDiscoveryManager$LeaseListenerImpl


      2. loop of relocation of pu instances
      ----
      The gsc heap dump for is attached to case 11037. Please download relocationStuck_cacheCloseMaxWait5.7z.001
      Run Test in jira : xap-13204 with com.gs.cache_context_close_max_wait 2 sec. and take heap dump after a while.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: