Hi,
In admin sections, I am reviewing Datagroups to monitor caching resets. However, although there is a cache invalidation in that datagroup, it is not reflecting there. Is there any where else that I can check? (I am 100% sure that the query and the model is the same while I am testing caches.)
Thank you
Solved! Go to Solution.
Yes. FYI - here is a publicly available page that lists Looker startup options, including a couple settings relating to cache settings.
https://cloud.google.com/looker/docs/startup-options
Although the page explicitly mentions Customer-Hosted instances, these settings are in play on Looker-hosted instances as well - but for Looker-hosted, only Looker ops team can adjust these settings (if necessary... typically in reaction to specific issues or because of an explicit request from the primary admin contact on the instance).
To be clear: I'm not fully convinced changing these settings will resolve your issue - I think more investigation / reproduction of the scenario needs to be done to be sure.
Though I don't have direct experience with this scenario, what I'm seeing from prior discussions indicates:
If the max_cache_storage size is reached then the looker invalidates the old cached results in the cache in order to store the new cache results.