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

Allow multiple MUC instances on one memcached server using cachestore_memcache

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Critical
    • Resolution: Won't Fix
    • 2.5.5, 2.6.2, 2.6.5, 2.7.2, 2.8
    • None
    • Caching
    • MOODLE_25_STABLE, MOODLE_26_STABLE, MOODLE_27_STABLE, MOODLE_28_STABLE
    • MDL-45375_master
      1. Setup different memcache backends for different stores
      2. Don't use memcache store for high-purge caches
      3. Write a custom plugin which ignores purges at own risk
    • Moderate
    • Hide
      1. Setup different Moodles in the same memcache store
      2. Purge caches of one of the Moodles
      3. Confirm that the other Moodle has its cache intact
      4. Create a course (one section of the cache will be purged)
      5. Confirm that the whole cache is not being purged
      Show
      Setup different Moodles in the same memcache store Purge caches of one of the Moodles Confirm that the other Moodle has its cache intact Create a course (one section of the cache will be purged) Confirm that the whole cache is not being purged

    Description

      memecache_store::purge() calls Memcache::flush() which wipes everything stored on that memcache server, not just the one MUC cache you think you are purging.

      In Moodle 2.6, where modinfo is stored in MUC, this can cause big performance blips. (See the graph in http://tjhunt.blogspot.co.uk/2014/04/load-testing-moodle-262-at-ou.html)

      Worse, if you are storing user sessions in the same Memcache store as MUC data, this can cause everyone to be logged out.

      Attachments

        Issue Links

          has been marked as being related by

          Bug - A problem which impairs or prevents Moodle from functioning correctly. MDL-50909 MDL-49489 Causes severe performance degradation of course index and search pages

          • Major - Major loss of function, incorrect output
          • Closed

          Improvement - An enhancement to an existing Moodle feature. MDL-45724 Detect the use of same memcached instance for both sessions and muc and warn about it

          • Critical - Crashes server, loss of data, severe memory leak
          • Closed
          will be (partly) resolved by

          Bug - A problem which impairs or prevents Moodle from functioning correctly. MDL-37145 Documentation for caching admin screens

          • Blocker - Blocks development and/or testing, prevents Moodle from running (applicable to bugs only)
          • Closed

          Improvement - An enhancement to an existing Moodle feature. MDL-48506 Improve memcached cache store so that it is multi-site safe

          • Critical - Crashes server, loss of data, severe memory leak
          • Closed
          will help resolve

          Bug - A problem which impairs or prevents Moodle from functioning correctly. MDL-49489 coursecontacts regularly (unnecessarily?) purging

          • Minor - Minor loss of function where workaround is possible
          • Closed
          links to

          Web Link Moodle in English: What to do about memcached cache reset

          Activity

            People

              Unassigned Unassigned
              timhunt Tim Hunt
              Damyon Wiese Damyon Wiese
              Matteo Scaramuccia, David Woloszyn, Huong Nguyen, Jake Dallimore, Meirza, Michael Hawkins, Raquel Ortega, Safat Shahin, Stevani Andolo
              Votes:
              13 Vote for this issue
              Watchers:
              21 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: