Job misfires, but notifications are sent long after the event occurs

Problem Description

 

Current Behavior

When a task in TAC is scheduled to run at different intervals of time, if any misfired event triggers, the notification mail is not sent exactly at that point in time. Instead, notification mails for all the misfired events will be sent at once.

 

Steps to reproduce

  1. Create a Job that takes 4 to 5 minutes (for example, with simple sleep ).
  2. In TAC, configure Mail Notification to your email address.
  3. Schedule the Job to run every minute.

The first run will be OK, but when the Job starts again, you will receive 10 mails at once with misfired notifications. This creates a big problem, as 4000 to 5000 emails are sent at a time when the tasks are encountered with misfired events.

 

misifred1.JPG

Expected behavior

Notification email should be sent exactly when the misfired event is triggered, or only one email should be sent specifying that the misfired events occurred. There is no such control, even to stop sending all emails at once.

 

misfired2.jpg

 

Root Cause

The behavior is considered to be bug in the product (TMC-11779).

 

Solution

The issue has been fixed by sending only one mail per task for misfired events at misfire checking. Request patch TPS-2259 from Talend Support.

Version history
Revision #:
2 of 2
Last update:
‎04-10-2018 07:14 PM
Updated by:
 
Contributors