Date |
|
Authors | |
Status | Documenting |
Summary | Overnight weekend GMC sync failed |
Impact | Data was left unsynchronised on Reval for half a day |
Non-technical Description
GMC sync failed - at their end we believeDue to GMC working on the Service on the Bank Holiday weekend. Data at our end didn’t initially sync. We spotted the problem, re-ran the jobs and all data on Reval is now back up to date.
...
- 01.05: Slack alert that the GMC sync failed.
- 08.40: Slack alert that the GMC sync was still failing.
- 14.51: GMC sync jobs were re-run successfully.
...
Root Cause(s)
Awaiting confirmationMaintenance on the GMC servers made the unreachable when the ETL ran, after the maintenance was completed we reran the jobs that were then completed successfully.
...
Action Items
Action Items | Owner |
|---|---|
Add section to GMC-Sync to check for connection before proceeding. | |
Add section to GMC-Sync to check for free disk space before proceeding | |
...
Lessons Learned
TBC.