Dispatcher cache invalidation | Community
Skip to main content
selvaganesh
selvaganesh
Level 5
October 16, 2015
Solved

Dispatcher cache invalidation

I have the dispatcher configured to point publish. Whenever I am publishing a page , the dispatcher invalidates the cache . I don't want the dispatcher to delete the cache immediately. I commented /invalidate , but still it is deleting the cache file.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
joerghoh
joerghohAccepted solution
Employee
October 16, 2015

Hi,

How do you want to the dispatcher to actually get the old data out of the cache? What's the stragey you would like ot have?

Kind regards,
Jörg

View reply

4 replies

Pawan-Gupta
Pawan-Gupta
Level 8
October 16, 2015

Did you configure and enabled "Dispatcher flush agent" on publish replication agent?? because that agent is also responsible to trigger the flush on dispatcher based on configured event.

Translate
joerghoh
joerghohAccepted solution
Employee
October 16, 2015

Hi,

How do you want to the dispatcher to actually get the old data out of the cache? What's the stragey you would like ot have?

Kind regards,
Jörg

Translate
selvaganesh
selvaganeshAuthor
Level 5
October 16, 2015

I am making http access calls to dispatcher  so that that dispatcher cache is made ready with new data during the publishing stage itself. Since dispatcher is invalidating it , the html files made by http access also gets deleted.

Translate
joerghoh
joerghoh
Employee
October 16, 2015

Hi,

so you are concerned about the fact, that files need to refetched from publish first and then being delivered to the browser? I think, that's the price you need to pay to fill up any cache ...

If you can live with stale data, you can omit the invalidation on a change, and rather invalidate time-base (using simply cron). After that you can start another script to fill the cache again.

kind regards,
Jörg

Translate
Terms & ConditionsAccessibility statement

Loading footer...