[SLING-5666] Unscheduling a job should remove corresponding node

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Event 4.0.0, Event 4.0.2
• Fix Version/s: Event 4.1.0
• Component/s: Extensions
• Assignee: Carsten Ziegeler
• Reporter: Damien Obrist
• Created: 15/Apr/16 12:45
• Updated: 02/Sep/16 16:30
• Resolved: 20/May/16 07:58

Description

Unscheduling a previously scheduled job does not remove the corresponding node below /var/eventing/scheduled-jobs:

ScheduledJobInfo info =  jobManager.createJob(topic).schedule().at(date).add();
// creates /var/eventing/scheduled-jobs/c204a1ad-b161-4e76-9dfe-4152bca088cf
info.unschedule();
// /var/eventing/scheduled-jobs/c204a1ad-b161-4e76-9dfe-4152bca088cf persists

This can lead to the situation where ScheduledJobHandler#scan picks the node back up again and reschedules the job.

This is a regression introduced by SLING-4680. Before the changes of SLING-4680, JobSchedulerImpl#unschedule took care of removing the node. Currently, this is not being done anymore.

Issue Links

• is duplicated by: SLING-6030 Unscheduling Cron-Jobs does not work