Skip to content

Rescue error if duration column range is exceeded

What does this MR do and why?

We had an incident where ActiveRecord::RangeError from PG:NumericValueOutOfRange was coming from UpdateProjectAndNamespaceUsageService and causing an incident as workers retry on the error.

This MR should mitigate that by rescuing but reporting on the error is raised. This will keep the worker from retrying over and over but we will still know that there was an issue adding the consumption because of the column size.

I've opened #404432 to change the columns to bigint.

It's worth noting that there is a monthly reset which means that the error is no longer being hit in April and likely we won't see it again until the end of the month.

Related to #403872 (closed)

How to set up and validate locally

Edited by Allison Browne

Merge request reports