Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-72564

OOM periodically with a growing size of config.xml

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker

      Description

      We've suffered from a periodically crush of jenkins in past a few months. After some investigation, we found out that the jenkins config.xml file size has been increasing periodically and finally lead to a OOME.

      What happened

      There are tons of hudson.slaves.EnvironmentVariablesNodeProperty declaring MAVEN_OPTS in our config.xml file,  and there's a screenshot showing how big this config.xml file is (we restart jenkins and reset this file periodically, and the first time we found out this problem, this file is up to 300mb big).

      What did we try

      We made config.xml file read-only by `chattr +i config.xml`, and found out that gradle plugin is trying to add MAVEN_OPTS every-time we start a pipeline job.

      What is weird

      Our jenkins is working with a kubernetes backend, and it seems like that it only happens when new pods are delivered by built-in node, but we've configured number of executors to 0 for built-in node.

      What i want to know

      1. why built-in node still taking job builds when its "number of executors" is zero?

      2. we've disabled gradle plugin to fix this problem, but what should we do if we need this plugin?

            welandaz Iurii Ignatko
            wangchen wang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: