/
2019-07-30 ElasticSearch Sync Job failed
2019-07-30 ElasticSearch Sync Job failed
Date |
|
Authors | Joseph (Pepe) Kelly |
Status | Complete |
Summary | |
Impact | None found. |
Root Cause(s)
ElasticSearch Sync job failed during the night at 1:34am (UTC) failed to complete.
The docker container restarted
Trigger
The TIS-SYNC restarted.
Resolution
Re-ran job as on Sync Service.
Detection
Alerting in Slack.
Action Items
Action Item | Type | Owner | Issue |
---|---|---|---|
Restart the jobs | Restore service | Joseph (Pepe) Kelly |
Timeline (BST)
- 2:34 am TIS-SYNC job failed
- 7.30 am Slack alerting of failed job in #monitoring (5 hour delay is to ensure all sync jobs running complete (or fail) before reporting on relative successes/failures - this has now been replaced by real-time reporting)
- 7.43 am Picked up alert and re-ran job (Ola)
- 7:48 am Re-run of jobs completed
, multiple selections available,
Related content
2023-08-14 Sync Service NI
2023-08-14 Sync Service NI
More like this
2021-06-14 Person ElasticSearch sync job failed affecting Person Search
2021-06-14 Person ElasticSearch sync job failed affecting Person Search
More like this
2021-02-12 Person Search Sync Failed
2021-02-12 Person Search Sync Failed
More like this
2021-02-08 Northern Ireland TIS Instance: ElasticSearch down
2021-02-08 Northern Ireland TIS Instance: ElasticSearch down
More like this
2017-01-06 ES Snapshotting error
2017-01-06 ES Snapshotting error
More like this
2023-07-19 TIS person search list - unable to find some doctors
2023-07-19 TIS person search list - unable to find some doctors
More like this
Slack: https://hee-nhs-tis.slack.com/
Jira issues: https://hee-tis.atlassian.net/issues/?filter=14213