DateneDate |
| ||||||||
Authors | |||||||||
Status | DocumentingDone | ||||||||
Summary |
| ||||||||
Impact | Unable to see the lists of doctors connected and under notice for revalidation |
| Table of Contents |
|---|
Non-technical Description
...
Why were no doctors showing in the revalidation recommendations and connections summary lists for most of the day? - Because the GMC overnight sync had failed
Why had the GMC overnight sync job failed? - Because the
gmc-client-servicekept crashing and restarting the sync processWhy did the
gmc-client-servicekeep crashing? - Because it was experiencing an out of memory error every time it received a response from GMC
It kept on crashing on startup because ?!?Why was the gmc-client-service experiencing an out of memory error every time it received a response from GMC? - current unknown
Why does it take so long for the GMC sync job to repopulate the doctors lists? - Because there’s a bottleneck in the CDC process (lambda)
...
Action Items | Owner | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
Reproduce error on preprod by spinning up task definition with less memory? | There’s a few minutes lag between calling the sync endpoint and the sync message showing up in rabbit, be patient and don’t trigger it multiple times | |||||||||
Dynamic modification of task definition: memory & CPU? | 💲 💲 💲 💲 💲 💲 | |||||||||
Small tasks/tidy up:
| Schedules reset Currently no need for parameters being different between environments | |||||||||
Can we improve the speed of the overnight sync job (particularly the CDC process from MongoDB via. the |
|
...