-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PSC-STM-A9: Switch over to live ingestion #248
Comments
Day 1 snapshot ingestion has started. |
Day 1 snapshot ingestion has completed. There were various invalid rows reported, but I'm guessing that's unrelated since it was the same process as is run for the monthly bulk data. |
Day 1 PSC stream ingestion has been started:
There were a few crashes, at first, with HTTP 504 returned in the JSON body causing a failure. That seems to have been a transient error—but we should keep an eye on it to see if it keeps occurring. Airbrake will report it, if so. It was necessary to set stdout sync in order for Heroku to report the correct status: |
Day 2 snapshot ingestion ingestion cannot be run until tomorrow (despite being actually Day 3 in this case), since it's necessary for today's data to appear in the PSC bulk snapshot: |
Airbrake fired overnight, notifying of a crash. Investigation showed that something went wrong, seemingly within Heroku, and the app eventually got relocated to another server:
From that excerpt, it seems that everything is working as it ought with regards to failure detection and restarts: note that timepoint 11103517 got run again after the first failure, and that timepoint 11103548 got processed again after the server relocation. Ideally, a single timepoint would be reprocessed only if it failed midway, not if processing completed. However, the Companies House Streaming API documentation says:
https://developer-specs.company-information.service.gov.uk/streaming-api/guides/overview And yet, it seems that the API returns the first event with that timepoint, not the first event after that timepoint. I don't think there's really anything we can do about this without diverging from the API documentation, and I'm not certain whether multiple events can ever have the same timepoint (it doesn't appear so, but I can't find anything definitive), so we'll just keep this as-is and reprocess the occasional event. |
Day 2 snapshot ingestion has started (although it is the 3rd day). |
Day 2 snapshot ingestion has completed successfully. |
To switch over, should happen over a 2 day period:
Day 1
Day 2
Estimate: 4 hours
The text was updated successfully, but these errors were encountered: