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

Implement Redis database selection in cache and session store

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 3.5.2
    • Authentication, Caching
    • None
    • MOODLE_35_STABLE
    • MDL-63641-redis-select-master
    • Hide

      Configuration

      Assuming an existing Redis installation...

      1. Browse to /cache/admin.php and modify your Redis store instance Database ID of any non-zero value. By default the number of databases is 16, on a range of 0 (default) to 15.

      Testing

      1. Verify that redis-cli monitor shows Moodle traffic issuing a SELECT n command before executing any others.
      Show
      Configuration Assuming an existing Redis installation... Browse to /cache/admin.php and modify your Redis store instance Database ID of any non-zero value. By default the number of databases is 16, on a range of 0 (default) to 15. Testing Verify that redis-cli monitor shows Moodle traffic issuing a SELECT n command before executing any others.

      If an administrator wishes to host multiple "things" (e.g. locks, MUC caches and session data) in a single Redis deployment it makes a lot of sense to isolate the data by database. This enables easier deployments, as purges of the keyspace can take place within a database, and more granular monitoring as per-database keyspace can be extracted from the deployment.

      Moodle currently offers the ability to do this only through a key name prefix.

            Unassigned Unassigned
            lukecarrier Luke Carrier
            Votes:
            4 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:

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