Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-2307

puppetserver 5.3 memory leak with jruby flushing

    Details

    • Type: Bug
    • Status: Needs Information
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: SERVER 5.3.3, SERVER 5.3.5
    • Fix Version/s: None
    • Component/s: Puppet Server
    • Labels:
    • Template:
      PUP Bug Template
    • Team:
      Server
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Puppetserver 5.3.5 appears to be leaking memory when jruby flushing via max-requests-per-instance is activated.

      We are running puppetserver in kubernetes and our 5.3.5 servers keep exceeding the allowed memory when the max requests setting is nonzero. The java process is limited to 8G heap space and also uses -XX:MaxRam but the memory usage increases until it hits the 12G limit and the pod is killed.

      We are running multiple different versions of puppetservers with identical settings (but different environments). Versions 2.4.0, 2.8.1, 5.1.5 are working fine, only version 5.3.x seems to be affected (tested 5.3.1, 5.3.3 and 5.3.5)

       

      The images are based on ubuntu xenial (16.04) and are using openjdk 8.
      The java memory settings are:
      -Xmx8G -XX:ReservedCodeCacheSize=512m -XX:MaxRAM=$(cat /sys/fs/cgroup/memory/memory.limit_in_bytes)

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  jtaylor Julian Taylor
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  8 Start watching this issue

                  Dates

                  • Created:
                    Updated: