Provide cluster invalidation mechanism for DBFlat cache
GENERAL
TESTING
GENERAL
TESTING
Description
relates to
Activity
Show:
Aaron Zeckoski March 27, 2012 at 12:35 PM
CLE team bulk inactive issues cleanup - if this is important then reopen or create a new issue
David Horwitz February 23, 2010 at 6:32 AM
MAINT TEAM REVIEW: This feature request is currently unassigned and will be reviewed. In line with stated Jira practice http://confluence.sakaiproject.org/display/MGT/Sakai+Jira+Guidelines Feature requests that are not going to be implemented will be closed with a status of "wont fix". If you intend implementing this issue please ensure that its up to date and assigned correctly
introduces caching on various property tables used by DBFlat.
Currently there is no cluster invalidation mechanism, which means that site properties (and other properties) may be up to 5 minutes out-of-date on other cluster nodes.
This could be problematic for some use cases, e.g. when Section Info is used for tutorial signup, a site property controls whether signup is available to students or not. Sometimes instructors switch this on at a particular time (e.g. 12pm) with a lab full of students waiting for it to go live.
This is to request cache invalidation across the cluster keyed to related events - for example site.upd should invalidate cache entries for site-related properties.