App Suite CacheService
8.51.0
SCR-1557
Summary: CacheService Database Server Load Optimization
Based on customer feedback and analysis of logs and metrics, we identified that the CacheService could generate significant database load spikes during scheduled cleanup operations. This behavior may negatively affect Core-MW database workloads when both services are configured to use the same database server.
The impact is most noticeable in environments where DocumentConverter(s) or ImageConverter(s) store millions of cached entries.
To address this issue, the underlying database structure has been redesigned. As part of the change, a database migration and cleanup of existing object store(s) are required. These steps are performed automatically during rollout, and no administrator action is normally required. In rare cases, such as temporary database connectivity issues during rollout or deployments on particularly slow clusters, manual intervention may be necessary. If CacheService logs continue to report database-related errors more than five minutes after the rollout has completed, administrators should restart the DocumentConverter and ImageConverter pods to re-establish their CacheService connections. The following improvements have been implemented in detail. Refactoring design decisions are linked as well: