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

« Previous Version 5 Next »

Date

Authors

Joseph (Pepe) Kelly Yafang Deng Jayanta Saha

Status

Documenting

Summary

Person sync jobfailed with exception [Unable to parse response body; nested exception is ElasticsearchStatusException[Unable to parse response body]; nested: ResponseException[method [POST], host

Impact

Non-technical Description

Notification alert received from monitoring prod that Sync job has stalled at early morning of 14th of August causing timeout in bulk upload.

Trigger

Detection

  • Failed job status noticed in the #monitoring-prod slack channel

Resolution

  • The Person Sync job was manually restarted and completed successfully.

Timeline

BST unless otherwise stated

  • 2:29am sync failed

  • 2:39am Sync [RevalCurrentPmSyncJob] started.

  • 07:36am - Sync [RevalCurrentPmSyncJob] manually reran

  • 07:36am - rerun of Sync [RevalCurrentPmSyncJob] completed.

Root Cause(s)

Action Items

Action Items

Owner

Lessons Learned

  • No labels

Slack: https://hee-nhs-tis.slack.com/
Jira issues: https://hee-tis.atlassian.net/issues/?filter=14213