Hi Frédéric, it seems to me that the redis cache is in memory to improve performance. the expiration of the cache content is managed by redis itself, but the database content in the hard disk must be cleaned by a separate process... but this needs to be confirmed, I'm not sure what I'm saying.
Le ven. 15 nov. 2024, 14:13, Frédéric Dussurget <[email protected]> a écrit : > Hi, > Correct me if I'm wrong but it looks as Redis caching is cleaning up > objects on its own ... based on the ticket TTL > https://apereo.github.io/cas/7.0.x/ticketing/Redis-Ticket-Registry.html > As I'm interested in this topic, I'll keep on an eye on following answers > to get more accurate info ... > Regards, > > Le jeudi 14 novembre 2024 à 14:43:31 UTC+1, wouldsmina a écrit : > >> Hello, >> >> I have set up CAS to perform a cleanup of the ticket registry (Redis), >> but at startup, I get a message saying that it is not enabled: >> 2024-11-14 14:26:21,575 INFO >> [org.apereo.cas.config.CasCoreTicketsSchedulingConfiguration] - <Ticket >> registry cleaner is not enabled to run on schedule. Expired tickets are not >> forcefully cleaned by CAS. It is up to the ticket registry itself to clean >> up tickets based on its own expiration and eviction policies.> >> >> cas.properties : >> cas.ticket.registry.cleaner.schedule.cron-expression=0 0 0 * * * >> cas.ticket.registry.cleaner.schedule.enabled=true >> >> CAS Version: 7.1.2 >> Java Version: 21.0.5 >> Tomcat Version: 10.1.6-1+deb12u2 >> >> Did I forget a parameter in the configuration ? >> >> Wouldsmina. >> > -- - Website: https://apereo.github.io/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/CAH2NqNbXHGtaKKa1VYtv9-0dNQNiYZ2NL6tng%2BUW-6aCPTsz2A%40mail.gmail.com.
