Hi everyone. We have a spryker application running on a Kubernetes CI cluster and recently we are h

U01A5ARAXP0

Hi everyone.

We have a spryker application running on a Kubernetes CI cluster and recently we are having some problems with redis pod filling the disk. After investigating, we found that it is full of sessions, which are getting created by each liveness probe every 5 seconds.

Anyone knows how to avoid this?

Christian von Schassen

Hi Flavio! If you don't get an answer from the community in a sensible timeframe, I'd suggest to create a support ticket at https://support.spryker.com

Valerii Trots

Please check if you have these modules:
https://github.com/spryker/session-redis/releases/tag/1.2.0
https://github.com/spryker/auth/releases/tag/3.7.0
https://github.com/spryker/session-redis-extension/releases/tag/1.0.0
Plus attached project level changes.

U01A5ARAXP0

Hi, thanks for the reply. I have session-redis v1.4.1, auth v3.7.5 and session-redis-extension v1.0.0.
We also have $config[AuthConstants::SYSTEM_USER_SESSION_REDIS_LIFE_TIME] = 20; on the config_default.php, and new SystemUserSessionRedisLifeTimeCalculatorPlugin()
on the SessionRedisDependencyProvider

Locally it seems to be fine, only one session is created for each browser calling the health-check endpoint. (forgot to mention that the liveness probe is configured to call that endpoint)

Valerii Trots

So you will need to find out what is going on yourself unfortunately. I haven't heard about other problems other than the fixed one from above.

U01A5ARAXP0

Ok, thanks anyway 🙏

giovanni.piemontese

I follow this thread.. we have also similar problem... (with a lot of not necessary yves/zed session in redis db that will be generated from health-check + our monitoring services check [yves and zed] ).

The problem is that the browser save your session cookie and via curl/monitoring tool there is no browser and the application in the response event dispatcher just check if sessionCookie exists otherwise create a new one (it means new session).

We have for a specific tool (java) already solved (found a workround) that the Tool via CookieManager will just send the cookie got in the first response to avoid this problem.

For Health-Check maybe we have to try the same or in best case the application should not create a new session for health-check/api/monitoring endpoint used for liveness probe.

U01A5ARAXP0

I guess we need a plugin similar to SystemUserSessionRedisLifeTimeCalculatorPlugin for the Yves SessionRedisDependencyProvider

U01A5ARAXP0

@valerii.trots I see now that on the Yves SessionRedisDependencyProvider, for the getSessionRedisLifeTimeCalculatorPlugins, you expect an array of plugins that implement a Zed interface... that is not correct, right?

U01A5ARAXP0

@valerii.trots do I need to submit a bug report for this or do you report it internally?

Valerii Trots

If there is an issue in Spryker, please create a support ticket. My colleagues will take care as I'm on vacation atm.

U01A5ARAXP0

ah, ok , thanks