Hi Steve, The cache gets invalidated after twice the length of the configuration option 'hss_reregistration_time', which has a default setting of 30 minutes.
To set this option, you should add hss_reregistration_time=<time in seconds> to /etc/clearwater/user_settings on each Homestead node and then restart Homestead. Note that it's not safe to set this to less than half the value of the configuration option reg_max_expires though (which defaults to 5 minutes). Our configuration options are documented at: https://github.com/Metaswitch/clearwater-docs/wiki/Clearwater-Configuration-Options-Reference. To force a refresh, there should be an option in the OpenIMS HSS to trigger a Push-Profile-Request, which will update Homestead. Ellie -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Steve Yeoman Sent: 14 August 2014 06:26 To: [email protected] Subject: [Clearwater] Homestead / Cassandra caching Hi, I've been experimenting with IFC Trigger Points in OpenIMS HSS and noticed that homestead keeps a cached copy of the triggers configured in HSS. So changes in HSS are not recognized straight away. How often does the cache in cassandra get refreshed? Is it possible to force homestead to do a refresh? or to flush the cache in cassandra? thanks Steve _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
