Closed zabeen closed 10 months ago
1) re-do test explained here: https://github.com/Anthony-Nolan/Atlas/issues/1053#issuecomment-1768760765 2) Check contents of the replayed update message and ensure the published datetime is correct
@zabeen Me and Daria tried to reproduce steps described here but we only saw that message appeared in matching-transient-a
and matching-transient-b
with old "PublishedDateTime" (we re-sent old message from yesterday in audit subscription) and we didn't see how it was moved there and any logs related to this process.
Maybe breaking SQL connection isn't enough to reproduce the situation when this algorithm could be tested?
Thanks @DmitriyShcherbina, I will investigate further.
SqlA
and SqlB
on DEV-ATLAS-MATCHING-DONOR-MANAGEMENT-FUNCTION by modifying username in the conn string. Save changes,updated-searchable-donors
topic, but will soon disappear from whichever sub represents the "dormant" db. It should remain on the "active db" sub until it dead-letters; this will take about 10-15 mins.PublishedDateTime
value in the message contents. Cleanup:
PublishedDateTime
: 2023-11-16T17:02:02.1772852+00:00
PublishedDateTime
: 2023-11-16T17:15:47.9513948+00:00
Test passed
Set PubishedDateTime here
Please also add unit test to cover this fix