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 Next »

Date

Authors

Joseph (Pepe) Kelly

Status

In-Progress

Summary

Impact

Applications were unable to fully use the message broker until RabbitMQ stopped synchronising nodes. After that a number of processing changes went through in significant numbers including overnight updates for Revalidation.

Non-technical Description

Trigger

.

Detection

.

Resolution

Timeline

  • - Stopped syncing a third node for of 2 queues being synchronised

5 Whys (or other analysis of Root Cause)

.

Action Items

Action Items

Owner

Comments

Lessons Learned

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.
 

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