Issue Summary

This is reproducible on Data Center: yes

The DVCS scheduler job runs by default every hour. Following the KB How to change the interval or schedule of the DVCS repositories sync and just running the DB update, we can change this, for instance, to run daily.
However, after restarting Jira, the interval is set back to one hour.

Using the jira-config.properties to define the system property dvcs.connector.scheduler.interval does not have an effect.

Steps to Reproduce

1. Go to Admin > Scheduler Services and expand the job "com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler:job"
2. Observe that the interval for the schedule is using one hour;
3. Update the interval, so after the next execution, it will use the new interval. On the sample below, the job should run daily:

UPDATE clusteredjob
SET interval_millis=86400000
WHERE job_runner_key='com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler';

4. Go to Admin > Scheduler Services and expand the job "com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler:job"
5. Observe that the interval for the schedule is now using one day. The next run will be executed, than it will calculate the next run using the new value of one day.
6. Stop Jira
7. Create the file jira.config-properties on the Jira home folder with the following content:

dvcs.connector.scheduler.interval=86400000

1. Start Jira

Expected Results

1. Go to Admin > Scheduler Services and expand the job "com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler:job"
2. The interval remains as one day.

Actual Results

1. The interval is set back to one hour.
2. The system property dvcs.connector.scheduler.interval was not used.

Workaround

• Add the JVM argument to the JVM arguments on startup in each of the nodes

  -Ddvcs.connector.scheduler.interval=86400000