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

RecurrencePeriod set too low?

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I notice a LOT of "ThinBackup Worker Thread" starting and finishing INFO messages in my jenkins.log file, so I am wondering if the RecurrencePeriod is set too low - does it really have to run every second? Even better, maybe allow it to be configurable by the user.

      Excerpt from log file:

      May 12, 2011 11:21:41 AM hudson.model.AsyncPeriodicWork$1 run
      INFO: Started ThinBackup Worker Thread
      May 12, 2011 11:21:41 AM hudson.model.AsyncPeriodicWork$1 run
      INFO: Finished ThinBackup Worker Thread. 1 ms
      May 12, 2011 11:22:41 AM hudson.model.AsyncPeriodicWork$1 run
      INFO: Started ThinBackup Worker Thread
      May 12, 2011 11:22:41 AM hudson.model.AsyncPeriodicWork$1 run
      INFO: Finished ThinBackup Worker Thread. 2 ms
      May 12, 2011 11:23:41 AM hudson.model.AsyncPeriodicWork$1 run
      INFO: Started ThinBackup Worker Thread
      May 12, 2011 11:23:41 AM hudson.model.AsyncPeriodicWork$1 run
      INFO: Finished ThinBackup Worker Thread. 2 ms
      May 12, 2011 11:24:41 AM hudson.model.AsyncPeriodicWork$1 run
      INFO: Started ThinBackup Worker Thread
      May 12, 2011 11:24:41 AM hudson.model.AsyncPeriodicWork$1 run
      INFO: Finished ThinBackup Worker Thread. 1 ms
      May 12, 2011 11:25:41 AM hudson.model.AsyncPeriodicWork$1 run
      INFO: Started ThinBackup Worker Thread
      May 12, 2011 11:25:41 AM hudson.model.AsyncPeriodicWork$1 run
      INFO: Finished ThinBackup Worker Thread. 0 ms
      May 12, 2011 11:26:41 AM hudson.model.AsyncPeriodicWork$1 run
      INFO: Started ThinBackup Worker Thread
      May 12, 2011 11:26:41 AM hudson.model.AsyncPeriodicWork$1 run
      INFO: Finished ThinBackup Worker Thread. 1 ms
      

        Attachments

          Activity

          Hide
          tofuatjava Thomas Fürer added a comment -

          the periode is set to every minute (as you can see in your logs) and not every second.
          it needs to run at least every minute because cron allows to specify minutes in the schedule. the spam of logs are generated from the jenkins-core which cannot be influenced with plugin code.

          So the only thing I could do is asking the core team to set the log level to something lower than info, otherwise the functionality of thinBackup get reduced.

          is this okay for you, and can I close the issue afterwards?

          Show
          tofuatjava Thomas Fürer added a comment - the periode is set to every minute (as you can see in your logs) and not every second. it needs to run at least every minute because cron allows to specify minutes in the schedule. the spam of logs are generated from the jenkins-core which cannot be influenced with plugin code. So the only thing I could do is asking the core team to set the log level to something lower than info, otherwise the functionality of thinBackup get reduced. is this okay for you, and can I close the issue afterwards?
          Hide
          pnyheim Paul Nyheim added a comment -

          Yes, that would be fine with me.
          Please update this issue with the reference to the new issue.

          Thanks.

          Show
          pnyheim Paul Nyheim added a comment - Yes, that would be fine with me. Please update this issue with the reference to the new issue. Thanks.
          Hide
          tofuatjava Thomas Fürer added a comment - - edited

          will be included in thinBackup plugin 1.3

          loglevel is reduced to FINEST so the logs aren't flooded anymore

          Show
          tofuatjava Thomas Fürer added a comment - - edited will be included in thinBackup plugin 1.3 loglevel is reduced to FINEST so the logs aren't flooded anymore
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: tofuatgit
          Path:
          pom.xml
          src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupPeriodicWork.java
          src/main/java/org/jvnet/hudson/plugins/thinbackup/hudson/model/AsyncPeriodicWork.java
          http://jenkins-ci.org/commit/thin-backup-plugin/bbcf283df82270d7ca96d08289b2d1c4028a9cf2
          Log:
          JENKINS-9669 - duplicate AsyncPeriodicWork and reduce log level from INFO to FINEST

          git-svn-id: https://svn.jenkins-ci.org/trunk/hudson/plugins/thinBackup@39505 71c3de6d-444a-0410-be80-ed276b4c234a

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: tofuatgit Path: pom.xml src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupPeriodicWork.java src/main/java/org/jvnet/hudson/plugins/thinbackup/hudson/model/AsyncPeriodicWork.java http://jenkins-ci.org/commit/thin-backup-plugin/bbcf283df82270d7ca96d08289b2d1c4028a9cf2 Log: JENKINS-9669 - duplicate AsyncPeriodicWork and reduce log level from INFO to FINEST git-svn-id: https://svn.jenkins-ci.org/trunk/hudson/plugins/thinBackup@39505 71c3de6d-444a-0410-be80-ed276b4c234a

            People

            • Assignee:
              tofuatjava Thomas Fürer
              Reporter:
              pnyheim Paul Nyheim
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: