Second-delay jobs are suitable for workloads that are sensitive to timeliness, such as near-real-time workloads that must continuously perform round robin. You can use the memory grid model and second-delay jobs to continuously handle a large amount of data. This topic describes how to create a second-delay job that runs on one job instance.

Second-delay jobs that you can create in SchedulerX are periodic jobs. Second-delay jobs if you want to execute simple Java jobs, distributed Java jobs, or Java scripts. In addition, you can use different methods to execute second-delay jobs.

Second-delay jobs are periodic jobs. To create a second-delay job, set Time type to second_delay and Fixed delay to 50 seconds when you create the job. For more information about how to create a job, see Create a job.

View the details of a second-delay job

For more information about how to view job instance details, see Job execution lists.

For a second-delay job, the Task instance records page also displays the Historical execution records tab. You can view the following information on this tab:

  • Execution records on the current day: the total number of times that the second-delay job was triggered, the number of successes, and the number of failures after the first time when the job was triggered on the current day.
  • Execution records on the previous day: the total number of times that the second-delay job was triggered, the number of successes, and the number of failures from the first time when the job was triggered on the previous day to the end of the previous day.
  • The most recent 10 execution results. The execution results include the total number of tasks that are distributed at each level, the number of successful tasks, and the number of failed tasks.

Configure alerting for a second-delay job

  • Execution failure alert. The alert is triggered only for the first time that a second-delay fails to be executed.
  • Consecutive execution failure alert. If the system completes a second-delay job for the first time but then consecutively fails to execute the job for more than 10 times, the system generates the alert.

To receive the preceding alerts, you must turn on the alerting switch in the alerting settings of the job.