Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Date

Authors

Andy Nash (Unlicensed)

Status

Complete

Summary

TIS NDW ETLs didn't run on Stage or Prod

Impact

Downstream NDW processes could not start

  • Root Cause(s)

  • Trigger

  • Resolution

  • Detection

  • Action Items

Root Cause(s)

  • The scheduled task didn’t execute

  • The build server (with the schedule) didn’t get triggered in the expected timeframe

  • Each new ‘ETL’ killed the previous one;

  • The build server was unavailable

  • Automated change requests caused a massive spike in load

Trigger

  • Unable to run the build on schedule

Resolution

  • Restarted Jenkins.

  • Manually triggered the tis-esr-etl-cron-applicant-export job and then the tis-esr-etl-cron-daily-export job.

  • Moved files to Monday’s 2020-08-03-outbound container.

Detection

  • Noticed while checking weekly ETL run

Action Items

Action Item

Owner

Issue

Trigger scheduled tasks differently.

  • No labels