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

Multiple cron instance running parallely

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.9.3, 1.9.4, 1.9.5, 1.9.6, 1.9.7, 2.3.7, 2.4
    • Fix Version/s: None
    • Component/s: Administration
    • Labels:
    • Database:
      Any
    • Testing Instructions:
      Hide

      Testing must be applied to each database as the locking mechanisms are different for each. We are only able to test PostgreSQL at this point in time.

      1. Apply Patch
      2. /usr/bin/php /path/to/moodle/admin/cli/cron.php
      Confirm cron runs all parts of the cron without error
      3. Run 5 copies of the script simultaniously;
      /usr/bin/php /path/to/moodle/admin/cli/cron.php
      Ensure that you get messages indicating parts were skipped due to locks
      4. Under Home ► Site administration ► Server ► Session handling
      Alter the setting of 'Use database for session information' and test again.

      This verifies cron. Now database locking needs to be verified.

      1. Under Home ► Site administration ► Server ► Session handling
      Ensure 'Use database for session information' is selected
      2. Login to Moodle
      3. Browse a number of pages to ensure you session stays operating

      Show
      Testing must be applied to each database as the locking mechanisms are different for each. We are only able to test PostgreSQL at this point in time. 1. Apply Patch 2. /usr/bin/php /path/to/moodle/admin/cli/cron.php Confirm cron runs all parts of the cron without error 3. Run 5 copies of the script simultaniously; /usr/bin/php /path/to/moodle/admin/cli/cron.php Ensure that you get messages indicating parts were skipped due to locks 4. Under Home ► Site administration ► Server ► Session handling Alter the setting of 'Use database for session information' and test again. This verifies cron. Now database locking needs to be verified. 1. Under Home ► Site administration ► Server ► Session handling Ensure 'Use database for session information' is selected 2. Login to Moodle 3. Browse a number of pages to ensure you session stays operating
    • Affected Branches:
      MOODLE_19_STABLE, MOODLE_23_STABLE, MOODLE_24_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      MDL-17783_cron_dup_master

      Description

      A new cron instance should not run if previous cron is still running.

        Attachments

        1. 0001-MDL-17783-cron-2_4.patch
          51 kB
          Russell Smith
        2. 0001-MDL-17783-cron-master.patch
          54 kB
          Russell Smith
        3. mdl_17783_cron_lock.patch
          39 kB
          Melissa Aitkin

          Issue Links

            Activity

              People

              • Votes:
                10 Vote for this issue
                Watchers:
                21 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: