Hi Team,
I have a question on Cache Policy.
When we have cache entries in Populate Cache Policy defined under some environment cache resource, how can we delete these entries stored as L2 cache on disk of cassandra node?
It seems that;
- Edge UI 'Delete' cache button only deletes cache resource but cache entries defined with <KeyFragment> for <CacheResource> doesn't seem to be deleted for L2 cache on disk
- InvalidateCache policy with PurgeChildEntries set to true doesn't delete the L2 cache entries on disk
- Expiration of Cache doesn't delete the cache entries on disk
Is it expected design of Cache Policy that L2 cache stays on disk unless it's explicitly deleted?
And, is the Management API to delete cache as follows the same behavior as Edge UI above?
curl -X DELETE https://api.enterprise.apigee.com/v1/organizations/{org_name}/environments/{env_name}/caches/{cache_...
Then can we have to delete L2 cache entries on Cassandra with the API?
curl -X DELETE https://api.enterprise.apigee.com/v1/organizations/{org_name}/environments/{env_name}/caches/{cache_...If it's not the case, how can we delete the cache entries on disk - only by cqlsh DELETE?
Since there are no configurable limit of L2 cache total size, it should be a problem with disk space just increasing to become full.
Actually a customer using L2 Cache with dynamically adding cache entries see the issue of overload of disk and 'nodetool repair' operation fails with large traffics possibly by this too many cache entries.
I would appreciate your advice on the best practice of deleting L2 cache when it becomes no more necessary.
Regards,
Toshi
LinkedIn
Twitter
