Talk:Redis cache store: Difference between revisions
From MoodleDocs
Tomasz Muras (talk | contribs) (Created page with "If you are configuring a cluster of Moodle servers/nodes, the Redis service (daemon) should be installed on an external server and all Moodle nodes (servers/instances) sho...") |
Tomasz Muras (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
If you are configuring a cluster of Moodle servers/nodes, the [[Redis]] service (daemon) should be installed on an external server and all Moodle nodes (servers/instances) should point to that external Redis. so all user's data is available when the user is using (connected to) any of the Moodle nodes, in case the user's connection is not persistent (sticky) to a specific node for the entire Moodle session. | "If you are configuring a cluster of Moodle servers/nodes, the [[Redis]] service (daemon) should be installed on an external server and all Moodle nodes (servers/instances) should point to that external Redis. so all user's data is available when the user is using (connected to) any of the Moodle nodes, in case the user's connection is not persistent (sticky) to a specific node for the entire Moodle session." | ||
This bit is not really correct, unless you meant only session cache: | This bit is not really correct, unless you meant only session cache: | ||
in case the user's connection is not persistent (sticky) to a specific node for the entire Moodle session | in case the user's connection is not persistent (sticky) to a specific node for the entire Moodle session | ||
Revision as of 14:07, 16 September 2019
"If you are configuring a cluster of Moodle servers/nodes, the Redis service (daemon) should be installed on an external server and all Moodle nodes (servers/instances) should point to that external Redis. so all user's data is available when the user is using (connected to) any of the Moodle nodes, in case the user's connection is not persistent (sticky) to a specific node for the entire Moodle session."
This bit is not really correct, unless you meant only session cache: in case the user's connection is not persistent (sticky) to a specific node for the entire Moodle session
