Geo: Inserting to job_artifact_registry causes a non-null database constraint
https://sentry.gitlap.com/gitlab/gitlabcom/issues/174367/
PG::NotNullViolation: ERROR: null value in column "missing_on_primary" violates not-null constraint
DETAIL: Failing row contains (26760, 2018-04-19 21:16:17.949156+00, 2018-04-19 21:16:59.943145+00, 0, 48118814, 1, null, null, null).
: INSERT INTO "job_artifact_registry" ("artifact_id", "bytes", "missing_on_primary", "retry_count", "retry_at", "created_at") VALUES (48118814, 0, NULL, 1, '2018-04-19 21:16:59.943145', '2018-04-19 21:16:17.949156') RETURNING "id"
What is the impact of this bug on 10.7?
The only source of artifact 404s that are not missing-on-primary that I am aware of is: artifacts that have been migrated to object storage before the secondary has synced them.
This will generate Sentry errors and errors in geo.log.
Each sidekiq job will retry 3 times before disappearing.
With the bug fixed, the artifact sync will be tracked as failed, and then periodically retried until MigratedLocalFilesCleanUpWorker
deletes the tracking record.
TL;DR the impact is noise in Sentry and geo.log.
Edited by Michael Kozono