[OAK-6605] Provide job name for async index update

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.7.7, 1.8.0
• Component/s: core
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 31/Aug/17 09:44
• Updated: 14/Sep/17 13:01
• Resolved: 04/Sep/17 07:21

Description

Starting with Sling Scheduler 2.6.0 runOn=SINGLE jobs are not scheduled exclusively on the leader anymore (SLING-5387). The implementation will try to distribute them evenly on all cluster nodes. The placement of these jobs depends on the name of the job, which is currently not set by Oak for the async index updates. In this case Sling will generate a name using the service id, but this is not guaranteed to be the same across all cluster nodes.

This means, it may happen that an async index update job is not scheduled at all, because all cluster nodes assume some other cluster node will schedule the job. Oak should therefore provide a name for the async index update jobs it schedules to help Sling identify those jobs.

Please note, there is a problem with the initial implementation of this feature in Sling, which got fixed in 2.7.0: SLING-7037

Issue Links

• is related to: OAK-6609 Provide job name for JournalGC and RevisionGC job
• relates to: SLING-7037 Scheduler does not retain provided name
• relates to: SLING-5387 Provide support for running singleton jobs on non leader cluster nodes also