You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tommaso Teofili (JIRA)" <ji...@apache.org> on 2014/10/02 12:32:33 UTC

[jira] [Created] (SLING-3993) Avoiding loops when syncing via coordinate agents

Tommaso Teofili created SLING-3993:
--------------------------------------

             Summary: Avoiding loops when syncing via coordinate agents
                 Key: SLING-3993
                 URL: https://issues.apache.org/jira/browse/SLING-3993
             Project: Sling
          Issue Type: Bug
          Components: Replication
            Reporter: Tommaso Teofili
            Assignee: Tommaso Teofili


In the case of a 'coordinate agent', sitting on 'author' instance, responsible for synchronizing 2+ 'publish' instances the simplest setup would consist of a 'queueing agent' (local exporter, no importer) sitting on each of the 'publish' instances with a trigger responsible of signaling changes of resources under a certain path so that when, for example, a resource 'bar' gets created under '/foo' the trigger will cause the creation of a package for '/foo/bar' which will be queued locally, the 'coordinate agent' will remotely fetch such a package from the queue of e.g. 'pub1' instance and remotely import it into 'pub2' instance.
If both 'pub1' and 'pub2' have the same trigger this may result into a looping scenario when instances keep exchanging packages for the same changed content.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)