Marcel Reutegger commented on SLING-7037:

bq. for whiteboard registered jobs: if a name is part of the properties, this 
name is used as is for the provided name; the name itself is still made unique 
using the service id.

Why is it made unique with the service id? I understand the service id may not 
always be the same across cluster nodes, which can result in a situation where 
a registered job with 'runOn:single' on multiple cluster nodes does not run at 
all. If I provide a name, shouldn't the scheduler use it as is? 

> Scheduler does not retain provided name
> ---------------------------------------
>                 Key: SLING-7037
>                 URL: https://issues.apache.org/jira/browse/SLING-7037
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: Commons Scheduler 2.6.0
>            Reporter: Marcel Reutegger
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>             Fix For: Commons Scheduler 2.6.4
>         Attachments: SLING-7037-test.patch
> The scheduler does not retain the provided name for the job as introduced in 
> SLING-5387.
> The value returned by the JobDataMap is a generated name that include the 
> service id.

This message was sent by Atlassian JIRA

Reply via email to