You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2014/07/08 13:14:04 UTC

[jira] [Updated] (SLING-3747) Provide a way to signal Jcr Installer to pause and resume scanning

     [ https://issues.apache.org/jira/browse/SLING-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra updated SLING-3747:
-----------------------------------

    Attachment: SLING-3747.patch

Initial patch which implements above approach.

Pending stuff
* Support for some kind of timeout. 


> 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
>         Attachments: 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)