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

Cache store instances do not report an error when the server is down.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.4.1
    • Fix Version/s: 2.4.2
    • Component/s: Caching
    • Labels:
    • Testing Instructions:
      Hide
      1. Install memcache
      2. Within Moodle create a memcached store instance.
      3. Map the new store instance to the calendar cache.
      4. Check it is ready.
      5. Set up a memcached test instance.
      6. Turn off the memcache backend (sudo /etc/init.d/memcache stop)
      7. Browse to the cache admin page and check the status column for the instance is red and has a help icon.
      8. Browse to the test performance script.
      9. Check that beside memcached it say "Store not ready"
      Show
      Install memcache Within Moodle create a memcached store instance. Map the new store instance to the calendar cache. Check it is ready. Set up a memcached test instance. Turn off the memcache backend (sudo /etc/init.d/memcache stop) Browse to the cache admin page and check the status column for the instance is red and has a help icon. Browse to the test performance script. Check that beside memcached it say "Store not ready"
    • Affected Branches:
      MOODLE_24_STABLE
    • Fixed Branches:
      MOODLE_24_STABLE
    • Pull Master Branch:
      wip-MDL-37935-m25

      Description

      There should be a way to test each cache instance to see if the server/folder is available or not and indicate this on the "Site administration / ► Plugins / ► Caching / ► Configuration" page.

      It is currently confusing when setting up new caches - how to tell if the cache is working?

      Also the performance tests do not indicate an error if a cache is down (they run even faster!).

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  11/Mar/13