Is there a way to prevent `[02-Jun-2021 08:54:58] WARNING: [pool worker] child 15 said into stderr:

U01LE4BMBK7

Is there a way to prevent [02-Jun-2021 08:54:58] WARNING: [pool worker] child 15 said into stderr: "[2021-06-02T08:54:58.797681+00:00] Yves.CRITICAL: Spryker\Shared\SessionRedis\Handler\Exception\LockCouldNotBeAcquiredException - Spryker\Shared\SessionRedis\Handler\SessionHandlerRedisLocking could not acquire access to the session d92b4810bf583771d7ed7728e478abfd in "/data/vendor/spryker/session-redis/src/Spryker/Shared/SessionRedis/Handler/SessionHandlerRedisLocking.php::97" {"exception":"[object] (Spryker\\Shared\\SessionRedis\\Handler\\Exception\\LockCouldNotBeAcquiredException(code: 0): Spryker\\Shared\\SessionRedis\\Handler\\SessionHandlerRedisLocking could not acquire access to the session d92b4810bf583771d7ed7728e478abfd at /data/vendor/spryker/session-redis/src/Spryker/Shared/SessionRedis/Handler/SessionHandlerRedisLocking.php:97)" in production? We're using Spryker Cloud.

U01LKKBK97T

https://documentation.spryker.com/docs/session-handlers?highlight=SESSION_HANDLER_REDIS%2[…]LER_REDIS_LOCKING%20%20%20%20%20Locked%20Sessions%20with

U01T075RRHD

Please be careful when not using the locking strategy. This might lead to session data loss.
From my experience, these issues usually are triggered by bots rapidly scanning your website.

U01LE4BMBK7

I was opening the shop myself

giovanni.piemontese

Known Problem.. Your FPM on YVES is maybe exited due SIGBUS or memory max child reached and all user connected and related to this fpm child process have still own session in redis locked (how long? default is max_execution_time from your php.ini * 0.8 as fraction).
After this time redis unlock (setEx) the sessions and the user can be again navigate..

It happens almost due fpm misconfigured or just not enough ram on yves server...

U01LE4BMBK7

thanks, that's a very good hint - will look into it!