Does a redis resets/forget his max-memory policy?

[tobiasb]

Since Cloudron v10 it is possible to set the redis maxmemoryPolicy via manifest.

We use redis for caching and set the allkeys-lru maxmemoryPolicy, but today since cloudron updated to 10.0.4, it seems the policy was reset to his default maxmemory-policy. The app could not caching anymore, because it reached the maxmemory, which can not happen with the policy.

[joseph]

@tobiasb can you inspect the redis container docker inspect <id> . It should have an env var named CLOUDRON_REDIS_MAXMEMORY_POLICY . Or you can docker exec the redis container and check env output.

[tobiasb]

I verify on another instance that cloudron did not set the maxmemoryPolicy/persistent config on a deployment, it was necessary to resave the redis service.

[girish]

Ah, this is probably a bug that policy changes are not applied on reconfigure . Should we consider this solved though? Since it's not very useful to go back and fix this.

[tobiasb]

I’ll be happy, when the policy and persistent config are kept on cloudron updates or when I install new app with such redis config and cloudron sets this as an initial config. However, this should also be documented on the add-on page.