Some more updates: The Sling Jobs Scheduler was contributed with https://issues.apache.org/jira/browse/SLING-3028 <https://issues.apache.org/jira/browse/SLING-3028> initially.
The relationship of Job Queues and the Job Scheduler are not clear to me though. It seems that the scheduled jobs are only executed in a dedicated single thread and have no relationship with Sling Job Queues at all. Can someone confirm this? Thanks, Konrad > On 06 Apr 2016, at 16:16, Konrad Windszus <konra...@gmx.de> wrote: > > In the past there was only one service for scheduling jobs [1] (completely > independent of Sling Jobs). Since Sling 7 it is even possible to schedule > Sling Jobs itself (which are persisted in the repository and may be > distributed in a cluster) [2]. > It would be really nice to have some documentation about the latter in [3] > and also to have some insights on when it is recommended to use which > approach. I understand that the scheduler service is more lightweight because > it does not persist anything in the repo. I would be in favour of deprecating > [1] and recommend everyone to only use Sling Jobs instead, then there is only > one API left for scheduled jobs. > > WDYT? > > Thanks, > Konrad > > 1 - > https://sling.apache.org/documentation/bundles/scheduler-service-commons-scheduler.html > 2 - > https://sling.apache.org/apidocs/sling7/org/apache/sling/event/jobs/JobBuilder.ScheduleBuilder.html > 3 - > https://sling.apache.org/documentation/bundles/apache-sling-eventing-and-job-handling.html > > >
