Blocked Job Configuration Properties | Teradata Data Mover - 17.11 - Blocked Job Configuration Properties - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
17.11
Release Date
October 2021
Content Type
User Guide
Publication ID
B035-4101-091K
Language
English (United States)
Property Description and Values
blocked.job.retry.enabled The property that determines whether Data Mover checks whether there are any locks on source or target objects prior to executing a job. If enabled and locks are detected, it tries again to run the job after a specified interval. If this property is not enabled, the other related properties listed below are ignored.
Specify one of the following options for the value element:
  • true: Data Mover detects locks and tries to start the job after the interval specified. The job is only run when there are no locks on objects.
  • false: Default. Data Mover does not check for object locks. If locks exist, the job hangs until locks are released.
blocked.job.retry.interval The time interval to wait if locks are detected before checking again whether the locks are still there. The default setting is 1 hour.
Specify values for each of the two elements:
  • value: specify the number of minutes or hours for the retry interval. Must be a positive integer.
  • unit: specify HOURS or MINUTES
blocked.job.retry.maxInterval The maximum interval for attempting to start any jobs blocked due to locks on source or target objects. Jobs are marked as failed after this interval is exceeded and they are still blocked. The default setting is 1 hour.
Specify values for each of the two elements:
  • value: specify the number of minutes or hours for the retry interval. Must be a positive integer.
  • unit: specify HOURS or MINUTES
blocked.job.maxAllowedLimit The maximum number of jobs that can be marked as blocked and re-tried. If a job is detected as blocked when this number is reached, the job is added to the job queue. The default value is 5. You may specify a different number for the value element, but it cannot be more than 25% of the maximum concurrent job limit.

Rules for the blocked.job.maxAllowedLimit property

  • The blocked.job.maxAllowedLimit value cannot exceed 25% of the maximum concurrent job limit. This is designed to prevent blocked jobs from consuming too many slots and preventing other jobs from running.
  • If a blocked job is detected when this limit has already been reached, the job is added to the job queue, even if the number of jobs already in the queue has reached the maximum queued jobs limit.
  • Attempting to save configuration.xml with a value greater than 25% of the maximum concurrent job limit results in an error.
  • If the maximum concurrent job limit value is changed when restarting the daemon, a value of 25% of the new maximum concurrent job limit is automatically used for the blocked.job.maxAllowedLimit property.