[ https://issues.apache.org/jira/browse/SLING-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra resolved SLING-3747. ------------------------------------ Resolution: Fixed Assignee: Chetan Mehrotra Implemented the above logic in http://svn.apache.org/r1617254 The logic would check for presence of any child node in path {{/system/sling/installer/jcr/pauseInstallation}} (default value) as an indicator that JCR integration should be paused. If no child is found the normal processing would be done > Provide a way to signal Jcr Installer to pause and resume scanning > ------------------------------------------------------------------ > > Key: SLING-3747 > URL: https://issues.apache.org/jira/browse/SLING-3747 > Project: Sling > Issue Type: New Feature > Components: Installer > Reporter: Chetan Mehrotra > Assignee: Chetan Mehrotra > Fix For: JCR Installer 3.1.8 > > Attachments: SLING-3747-1.patch, SLING-3747-2.patch, SLING-3747.patch > > > Currently Sling Installer JCR Provider would listen for observation event and > would perform a rescan every 500 msec upon receiving any observation event. > This at times cause issue when large number of bundles get updated in > repository say via installation of bug fixing content package. Further if > same content package also updates the repository bundle then it causes issues > as repository bundle might get updated midway while content package is still > being deployed > Based on [~fmeschbe] suggestion this can be done via introducing a signalling > mechanism between component which installs package and JCR Installer. It > would work something like this > # JCR Installer would listen to changes done to property > {{/system/sling/installer/jcr/pauseInstallation}} > # Package installer would set the above flag to true before installing the > package and reset it back to false post installation > # If JCR Installer detects that flag is set to true it would not scan the > watch folders untill it get reset back to false > This should also address the issue in cluster deployment -- This message was sent by Atlassian JIRA (v6.2#6252)