...
- If a transaction failure occurs the JobScheduler Master will try to rollback the transaction and will disconnect from the database.
- If the connection to a database gets lost or if a transaction failure occurs then the JobScheduler Master will try to re-connect every 60s.
Jira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1032 Jira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1283 - A Master single instance can be configured to repeat an unlimited number of connection attempts.
- A Master Active Cluster member requires the database connection to become available within less than 120s. Otherwise the cluster member terminates in order to prevent duplicate execution of jobs in the cluster
- In case of Database Connection Loss the JobScheduler Master will switch to paused mode, i.e. any execution of new tasks will be postponed.
Jira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1511 - If the connection to the database can be re-established within the same JobScheduler session then all postponed tasks will be executed immediately.
- If the connection to the database is established after a JobScheduler restart then
- previously enqueued tasks will be executed immediately.
- start times for scheduled tasks will be re-calculated, i.e. tasks that have been scheduled for the period in which the JobScheduler was not active will not be executed.
...