Dispatcher cache getting auto flushed

[AK86]

Hi All,

We are facing issue with dispatcher cache. The cache getting deleted from server which causing performance issue as the content has to be served from publish environment. We have just configured dispatcher flush on author instance. Is there any way to identify if flush is getting trigger automatically? Anything we need to check at dispatcher.any file? Also how we can avoid auto flush the dispatcher cache.

[Sachin_Arora_]

Please check the logs of Cache Invalidate agent. You can set the log level to Debug and see the flush requests.

You will be able to see property CQ-Path which would be the path of resource getting invalidated. 

If you dont see any logs of invalidation in Agent, please check if there is any ACS Dispatcher Flush rule configured in AEM. Link : https://adobe-consulting-services.github.io/acs-aem-commons/features/dispatcher-flush-rules/index.ht...

Also you can check the logs of dispatcher and see from where request is coming for flushing the cache.You may need to increase log level to DEBUG to check this.

[AK86]

Hi @Sachin_Arora_ - Thanks for the inputs. However we have disabled flush agents from last 2 days so no logs are there for the same. We also checked Osgi configuration but nothing is configured. Is there anything that we need to address at dispatcher level or any auto invalidation happen from author that we are investigating. kindly provide your input on this.

[Sachin_Arora_ · Accepted solution]

@AK86 Thanks for update. As you mentioned flush agents are disabled, I don't think there should be any other way invalidating cache from AEM, assuming there wont be any custom logic written in backend to invalidate cache on an event.

Please confirm is it happening after activation of any content or its happening after a period of time? Is it cleaning whole cache or any particular content?
Also please check in dispatcher log if there is any request coming for invalidation.

[arunpatidar]

Hi,

Please check the .statfile level.

https://www.axamit.com/blog/adobe/dispatcher-4 

This could be the issue of invalidating/deleting entire cache with every publish.