invalidate cahce-dispatcher flush agent

[msina]

Hi,

I have a query about dispatcher flush agent invalidate cache.

We have configured dispatcher flush agent on publishing instance.

When we update any page in author e.g update the image then we can see the change appears in publisher and dispatchers.

But when we check in the dispatcher server

/opt/communique/dispatcher/cache/test/multiple-image-test/_jcr_content/root/responsivegrid/image.coreimg.png

[root@dis01 image.coreimg.png]# ls -ltr

total 128

-rw-r--r--. 1 apache apache 90438 Aug  9 11:28 1533828434065.png

-rw-r--r--. 1 apache apache 36339 Aug  9 11:29 1533828539134.png

We see both images there.

Isn't it the first image should get deleted?

regards

Sina

[Jörg_Hoh]

No, the invalidation is kind of lazy; files are only marked as invalid, but not deleted; except the page/asset which is replicated and therefor causes the invalidation. But all other pages and assets remain as file in the cache.

[msina]

What do you mean by "kind of lazy"? Will AEM delete the images later on? What is out of the box house keeping for these images?

Do we need to make our customized script to delete ?

[Jörg_Hoh · Accepted solution]

It remains as stale file in the cache. If it's getting requested, the dispatcher will refetch it from AEM and then store it in the cache as "fresh" content. No need to implement a custom purge or delete to deliver current content.

(Nevertheless you might run a complete delete of the cache from time to time. If you remove pages or assets from AEM publish by deactivation, the stale files remain in the cache undefinitly, unless you don't clean them up manually.)

Jörg

[msina]

Thanks for the clarification.