Details
-
Type:
Feature Request
-
Status: RESOLVED
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 20.0
-
Fix Version/s: 21.0 [Tentative]
-
Component/s: Global
-
Labels:None
-
20 status:Won't Fix
-
19 status:Won't Fix
-
12 status:Won't Fix
-
11 status:Won't Fix
-
10 status:Won't Fix
-
Test Plan:
Description
Sakai would see great benefits from a distributed cache however the some of the dense objects that are cached pose serialization issues and have traditionally prevented the use of a distributed cache. However this is not the case for Hibernate L2 caching and so we could look at leverage something like Apache Ignites Distributed Hibernate L2 cache.
A distributed cache inherently solves the cache invalidation issues between multiple nodes and has many improvements some of which are described in SAK-25476 like:
- removes the need for cache invalidation logic
- less database calls and cache ttl's can now be much higher
- warm caches on node restarts
- lower memory requirements
Gliffy Diagrams
Zeplin
Attachments
Issue Links
- is depended on by
-
SAK-43773 Ignite Spring Cache Manager should use existing ignite instance
-
- RESOLVED
-
-
SAK-43776 Improved Ignite networking configuration for multiple instances on the same server
-
- RESOLVED
-
-
SAK-43786 Kernel configure Ignite caches to favor reads by default
-
- RESOLVED
-
-
SAK-43804 Update Apache Ignite to version 2.8.1
-
- RESOLVED
-
-
SAK-43843 T&Q: Stacktrace when instructor refreshed Assessments page while students are in timed test
-
- Verified
-
- is related to
-
SAK-43799 SAMIGO - Question pool don't work
-
- RESOLVED
-
-
SAK-43837 SAMIGO - Student submissions don't appear
-
- RESOLVED
-
- relates to
-
EVALSYS-1594 Add Apache Ignite as Spring jCache/Hibernate provider
-
- Awaiting Review
-
-
SAK-25476 Support a distributed cache layer underneath ehcache
-
- RESOLVED
-