Опубликовано Alain Raap

I found these settings of Redis in my phpinfo page:

redis.session.lock_expire 0 0
redis.session.lock_retries 10 10
redis.session.lock_wait_time 2000 2000
redis.session.locking_enabled 0 0

These are (default) values of the phpredis extension, how should they be configured for Moodle (besides
the settings in config.php of Moodle)?
Giuseppe, do you still have these problems with Redis? I saw this tracker https://tracker.moodle.org/browse/MDL-68577?attachmentOrder=desc that also explains this setting for Redis $CFG->session_redis_acquire_lock_retry. Although I see in the code of lib/classes/session/redis.php that this field is already set with 100 as a default value:

    /** @var int $lockretry how long to wait between session lock attempts in ms */
    protected $lockretry = 100;


We ran into the same problem (and with nearly the same Linux stack), so I'm curious if you already found a solution. 
We're still searching for a solution to solve the session lock problem.

I just found this tracker, maybe this could explain the timeouts?

https://tracker.moodle.org/browse/MDL-72796

Thanks for sharing this interesting information and the presentations! Will there be organized a next event? I see several flavours with / without Cloud solutions and also different solutions with docker / kubernetes and AWS, very interesting.
If you want some more info, just send me a PM. We use Ansible Tower which makes it easy to run playbooks for install/update/delete plugins and install/upgrade Moodle on our Moodle OTAP environment. Also a great tool for housekeeping and system upgrades.
Daniel upgrading Moodle needs some thoughts about how to do this with less effort. I've built an Ansible playbook that calls several shell scripts and also copies the installed plugins to a fresh version of Moodle. The Moodle software and language pack are fetched with git and installed with the cli upgrade script. This works fine now for our Redhat Linux environment.