Closed bcavns01 closed 6 years ago
Was a data issue server side, should be fixed - can you rerun a fresh sync to confirm, please?
Thank you. Rerun made it to the end without error. Is there a UTC time window where we should avoid attempting to sync, or an api endpoint for checking peeringdb status to know that it's in the process of updating?
Generally you should be fine to sync whenever, personally i'd avoid UTC 00:00 simply because it's a very common time where everyone runs their sync, so it might be slower than others.
The sync on a fresh database uses cached responses that are refreshed roughly every 15 minutes.
Incremental syncs after the initial ones get realtime responses.
During a full sync of of peeringdb, the sync is crashing. We followed the tickets that were similar to this, regarding failures during subsequent syncs, and the proposed solutions were to delete the database and perform a full sync, which we now do.
Prior to all syncs, we delete all peeringdb tables/databases and allow them to be rebuilt; however, we're now starting to see the same sync errors even when it's a fresh sync with no pre-existing data in the database.