Debugging Content Delivery embedded caching
A variety of issues can arise with embedded caching on the server. This topic explores what could be wrong, and how you might debug the problem.
About this task
- The microservices may fail to connect to Apache Ignite, the caching backend
- When caching takes place across multiple hosts, issues may arise, like the question which host starts first when caching is started up.
- Objects may not get flushed from the cache. This issue should always eventually resolve itself when the TTL (Time to Live) of the object expires.
The bullets above could be checked with simple self-made logger/controller. Alternatively, the customer could just examine Ignite's own logging (statistics). Ignore entries that require a key.