Accessing Nodes while package installation

[Jai1122]

Hi All,

    I would like to know how aem behaves if user requests  a resource which is getting updated by package installation.  In our case, a particular node has a list of json files as children. A certain activity by author will create a package of all this json nodes and replicates it to publish and also custom replication handler will flush the dispatcher cache of the json files. If user requests one of the json files, since the json is not available in cache, request will hit publish instance. But package installation is not completed yet. Now there are two possible outcomes.

1) AEM can hold the request for package installation to complete and then serve the json.

2) AEM can simply serve the old or existing json.

I think AEM will pick option2 but under certain load behaviour seems to be option1. Also, if a package has say 50 json, will AEM update the json files in repo, one by one or it is a bunch update? At least as per logs in package manager it seemed to me to be one by one. If so, assume at a given moment one.json is getting updated by package install and user requests say, five.json, what will be the behaviour?

Kindly enlighten me with your thoughts.

We are using AEM v6.4.5

Regards,

Jayapal.S

[BrianKasingli]

@Jai1122 

You should always continue to serve the old code deployment via cached pages until after another code deployment is complete. Once the new code deployment is complete, then you can manually flush the cache to serve new initiatives to the end-user.

You can automate this, anthoer option is that you can have your content authors update all the children nodes when (cq:Page) is the parent. You activate the page, and then using a tool like ACS Commons dispatcher flush rules, you can flush the .json files from the webserver, to show new content authored items from the .json file request, https://adobe-consulting-services.github.io/acs-aem-commons/features/dispatcher-flush-rules/index.ht....

[SureshDhulipudi · Accepted solution]

you can set /serveStaleOnError in dispatcher to serve stale content.

https://helpx.adobe.com/experience-manager/kb/ServeStaleContentOnError.html