clearing and refetching bulk content

Avatar

Avatar

Adilmo

Avatar

Adilmo

Adilmo

30-03-2021

We need to bulk publish content (10000s of pages).  They are created as a scheduled event so require almost immediate publish for all the pages in one go.  Main challenge is how to invalidate content on dispatcher (10000s of pages) and then re-fetch these pages again (on multiple dispatchers). 

 

What is the best strategy to do this ?? Is there a possibility of leveraging network storage for dispatcher cache??

 

 

Dispatcher replication Replication Performance Issues

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Jörg_Hoh

Employee

Total Posts

3.1K

Likes

1.0K

Correct Reply

1.1K

Avatar

Jörg_Hoh

Employee

Total Posts

3.1K

Likes

1.0K

Correct Reply

1.1K
Jörg_Hoh
Employee

01-04-2021

Answers (2)

Answers (2)

Avatar

Avatar

Umesh_Thakur

MVP

Avatar

Umesh_Thakur

MVP

Umesh_Thakur
MVP

04-04-2021

As @Jörg_Hoh  mentioned, you can go with the re-fetching flush agent for this purpose with some modification. If number of pages are 10k then refetching al those 10k pages will flood your publisher with request from dispatcher and again will be a performance issue for you so it will be better to re-fetch only very frequent page out of those 10k like homepage and all and cache all other pages on user request. With the help of java you can use path URL to allow re-fetching.

Hope this will help.

Umesh Thakur

Avatar

Avatar

asutosh_j3

Avatar

asutosh_j3

asutosh_j3

30-03-2021

Hi @Adilmo 

You can issue an HTTP request that causes the dispatcher to delete cached files, and immediately retrieve and recache the file.

Delete and immediately re-cache files when web sites are likely to receive simultaneous client requests for the same page. Immediate recaching ensures that Dispatcher retrieves and caches the page only once, instead of once for each of the simultaneous client requests.

 

POST /dispatcher/invalidate.cache HTTP/1.1
CQ-Action: Activate
Content-Type: text/plain
CQ-Handle: /content/something/en_us/123.html
Content-Length: 12

/content/something/en_us/123.html

 

Also, you can write a flush-cache servlet which can send an invalidate request to Dispatcher and can recache the content. Please take necessary precautions while implementing the flush-cache servlet. Please see the link below for more details:

https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/page-invalid...

 

Hope this helps!

Thanks!