Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-73748

All sites check for available updates on the hour, every two hours

XMLWordPrintable

    • MOODLE_310_STABLE, MOODLE_311_STABLE, MOODLE_39_STABLE
    • MOODLE_311_STABLE
    • MDL-73748-master-check_for_updates
    • Hide

      Note: The point of the test is to make sure that the upgrade step works as expected in two different scenarios.

      Default schedule is reset during the upgrade

      1. Prepare a fresh default installation of a recent released version.
      2. Log in as admin.
      3. Go to Site administration > Server > Tasks > Scheduled tasks.
      4. Locate the "Check for updates" (\core\task\check_for_updates_task) and confirm it is using the default schedule - minute: 0, hour: */2
      5. Upgrade the site to the patched version.
      6. Locate the "Check for updates" task again.
      7. TEST Check that the task is now using a new schedule and both minute and hour is set to a random value.

      Custom schedule not affected by the upgrade

      1. Prepare a fresh default installation of a recent released version.
      2. Log in as admin.
      3. Go to Site administration > Server > Tasks > Scheduled tasks.
      4. Change the schedule of the "Check for updates" (\core\task\check_for_updates_task) to some non-default value.
      5. Upgrade the site to the patched version.
      6. Locate the "Check for updates" task again.
      7. TEST Check that the task is still using your custom schedule and was not changed during the upgrade.
      Show
      Note: The point of the test is to make sure that the upgrade step works as expected in two different scenarios. Default schedule is reset during the upgrade Prepare a fresh default installation of a recent released version. Log in as admin. Go to Site administration > Server > Tasks > Scheduled tasks. Locate the "Check for updates" (\core\task\check_for_updates_task) and confirm it is using the default schedule - minute: 0, hour: */2 Upgrade the site to the patched version. Locate the "Check for updates" task again. TEST Check that the task is now using a new schedule and both minute and hour is set to a random value. Custom schedule not affected by the upgrade Prepare a fresh default installation of a recent released version. Log in as admin. Go to Site administration > Server > Tasks > Scheduled tasks. Change the schedule of the "Check for updates" (\core\task\check_for_updates_task) to some non-default value. Upgrade the site to the patched version. Locate the "Check for updates" task again. TEST Check that the task is still using your custom schedule and was not changed during the upgrade.

      Checking traffic on our update server we're seeing hourly spikes that increment the server load. This is caused mainly because:

      • Over 90% of request are happening on the hour
      • Requests are happening every 2 hours

      Spikes could be easily reduced if that task:

      • is run twice per day and/or
      • is run in random minutes instead of the hour

      Considering it would be applied only in updated sites and load is getting higher it would be great if the modification is accepted and issue is integrated.

      Thanks in advance!

        1. MDL-73748_Test Passed.PNG
          MDL-73748_Test Passed.PNG
          43 kB

            mudrd8mz David Mudrák (@mudrd8mz)
            eduardcercos Eduard Cercós
            Victor Déniz Falcón Victor Déniz Falcón
            Andrew Lyons Andrew Lyons
            Gladys Basiana Gladys Basiana
            Votes:
            1 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 4 hours, 25 minutes
                4h 25m

                  Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.