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

Detect the use of same memcached instance for both sessions and muc and warn about it

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide
      1. Prepare a memcache server if you've not already got one up.
      2. Configure Moodle sessions to use memcache (see $CFG->session_memcached_save_path)
      3. Configure a Memcache cache store to use that same memcache server.
      4. Observe that you get a warning on the Cache configuration page about using the same memcache serve for both MUC and sessions.
      Show
      Prepare a memcache server if you've not already got one up. Configure Moodle sessions to use memcache (see $CFG->session_memcached_save_path) Configure a Memcache cache store to use that same memcache server. Observe that you get a warning on the Cache configuration page about using the same memcache serve for both MUC and sessions.
    • Affected Branches:
      MOODLE_26_STABLE, MOODLE_27_STABLE
    • Fixed Branches:
      MOODLE_26_STABLE, MOODLE_27_STABLE
    • Pull Master Branch:
      45724-28
    • Pull Master Diff URL:

      Description

      Right now it's possible to use the same memcached instance with moodle for both php sessions and muc store.

      memcached implementation has a well-known (MDL-45375) inability to invalidate/purge group of keys, so current implementation simply deletes everything on purge of any cache.

      That can hit php sessions being deleted together with MUC contents, and that can lead to real problems, invalidating moodle sessions in the middle (of a quiz, of a post...).

      So it would be great to articulate some way to detect if the same memcached instance is being used for both php sessions and muc and warn, loud and in red about the risks of such combination.

      Perhaps with a "fixed" key, or comparing settings or whatever. And to be shown in the admin notifications or in environment info or wherever.

      Anything visible enough. Ciao

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                4 Vote for this issue
                Watchers:
                14 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  8/Sep/14