Hello there, I am trying to test the distribution of sling jobs across clusters which do NOT share the same repository.
I have set up 3 instances I1, I2 and I3 each alone in its cluster and I have configured *org.apache.sling.discovery.oak.Config* on I2 and I3 to have the topology connector url point to I1. A job consumer for topic T1 is running on I1 and when I open /system/console/slingevent on I2 or I3 I can see that the topic T1 is displayed and listed under the sling id of I1. So topology is working. When I start a job for example on I2 with topic T1, the job consumer for T1 on I1 is not executed. But in the I2 repo I can see that a node is created for that job: /var/eventing/jobs/assigned/*<I1-sling-id>*/*<T1>*/<year>/<month>/<day>/<hour>/<minute/<id> and it looks like it is properly assigned to I1. But as said the job consumer on I1 is not executed. Could you please first confirm that job distribution across clusters that do NOT share the same repository is supported? Reading through slides from Carsten Ziegeler on slideshare, I had the impression that it is supported. If supported could you please tell me what I am doing wrong/missing? Regards, -- Nono Junang Technical Director InsideAEM Limited 38 Waingaro Lane, RD 3 Kerikeri 0293 M +64 21 400 319 W www.insideaem.com
