service-fabrik-scheduler job from service-fabrik/3.140.0
              Github source:
              ad98d3b or
              master branch
            
Properties¶
agenda_collection¶
  
    
      Name of the collection in mongodb which is to be used by agendaJS to store the scheduled job meta info
- Default
- agendaJobs 
default_concurrency¶
  
    
      A number which specifies the default number of a specific job that can be running at any given moment
- Default
- 20 
default_lock_lifetime¶
  
    
      Specifies the default lock lifetime of a batchjob in milliseconds. A job cannot be re-run when within this locktime period (in case of errors, crash etc.)
- Default
- 180000 
downtime_maintenance_phases¶
  
    
      Maintenance phases during which (even any one of them) the scheduler must be shut down as ZDM is not in place across dependent components
- Default
- - BROKER_DRAIN_INITIATED 
job_history_retention_in_days¶
  
    
      Retention period in number of days, for which the job run history is maintained. (for ex. 30 - job run history for 30 days will be maintained)
- Default
- 30 
job_types¶
  
    
      Comma seperated list of batch job types that are enabled in service fabrik. Jobs can be enabled disabled by changing this list.
jobs¶
  
  
    
reschedule_delay¶Jobs when found to be conflicting with each other are rescheduled after this delay (human-interval)
- Default
20 minutes from now
scheduled_backup¶
max_attempts¶If an update is in-progess while backup is to be run, then the backup will be rescheduled after a delay. This will be repeated for the below configured times if update is long running
- Default
3
service_instance_update¶
max_attempts¶In case of an error while trigerring an update, max retry attempts will be done based on the below configured value (note errors due to running backups are not considered)
- Default
3
run_every_xdays¶Runs the service instance update job once every configured number of days
- Default
7
should_start_after_hr¶Service instance update job schedule is randomized but this param specifies the start time (hrs) after which the randomization must be done
- Default
7
should_start_after_min¶Service instance update job schedule is randomized but this param specifies the start time (mins) after which the randomization must be done
- Default
0
should_start_before_hr¶Service instance update job schedule is randomized but this param specifies the start time (hrs) before which the randomization must be done
- Default
16
should_start_before_min¶Service instance update job schedule is randomized but this param specifies the start time (mins) before which the randomization must be done
- Default
59
time_zone¶Timezone in which the service instance update job runs
- Default
Asia/Kolkata
maintenance_check_interval¶
  
    
      Once scheduler is placed in maintenace mode, it checks every configured (ms) for status of maitenance mode
- Default
- 90000 
maintenance_mode_time_out¶
  
    
      (ms) - wait for sf deployment to complete. Beyond this timeout out time scheduler starts
- Default
- 3.6e+07 
max_concurrency¶
  
    
      A number which specifies the max number of batch jobs that can be running at any given moment
- Default
- 30 
max_workers¶
  
    
      Max number of Job process workers
- Default
- 2 
process_every¶
  
    
      Interval at which scheduler will query the database looking for jobs that need to be processed
- Default
- 1 minute 
run_with_web_process¶
  
    
      Flag which indicates if scheduler can run in the same process as that of service fabrik broker web process
- Default
- false 
scheduler¶
  
  
    
name¶Name of the service fabrik job scheduler
- Default
service-fabrik-scheduler
start_delay¶
  
    
      Scheduler start must be delayed for DB connections to happen
- Default
- 120000 
system_jobs¶
  
  
    
archive_metered_events¶
interval¶Cron expression defining schedule interval for archive_metered_events job
- Default
0 */4 * * *
job_data¶
events_to_patch¶Number of events to patch in one job run
- Default
500
backup_reaper¶
interval¶Cron expression defining schedule interval for backup reaper job
- Default
0 1 * * *
job_data¶
delete_delay¶delay in processing between two tasks (in millisecond)
- Default
1000
dbcollection_reaper¶
event_detail¶
retention_in_days¶Retention period in days for the event details (create_backup/update_instance) stored in SF. Data older than this is deleted
- Default
90
interval¶Cron expression defining schedule interval for db collection reaper job
- Default
0 2 * * *
jobrun_detail¶
retention_in_days¶Retention period in days for the agenda job run details. Data older than this is deleted
- Default
60
meter_instance¶
enabled¶true if metering is enabled
- Default
false
interval¶Cron expression defining schedule interval for metering job
- Default
0 2 * * *
Templates¶
            Templates are rendered and placed onto corresponding
            instances during the deployment process. This job's templates
            will be placed into /var/vcap/jobs/service-fabrik-scheduler/ directory
            (learn more).
          
- bin/job_properties.sh(from- bin/job_properties.sh.erb)
- bin/service-fabrik-scheduler_ctl(from- bin/service-fabrik-scheduler_ctl.erb)
- config/circuit-breaker-config.yml(from- config/circuit-breaker-config.yml.erb)
- config/eventlog-config-external.yml(from- config/eventlog-config-external.yml.erb)
- config/eventlog-config-internal.yml(from- config/eventlog-config-internal.yml.erb)
- config/settings.yml(from- config/settings.yml.erb)
Packages¶
            Packages are compiled and placed onto corresponding
            instances during the deployment process. Packages will be
            placed into /var/vcap/packages/ directory.