-
Bug
-
Resolution: Done
-
Normal
-
None
-
None
-
False
-
-
False
-
-
When looking at logs for stage you can see that there every night we see a successful completion message of "PurgeSnapshotsJob job complete! Exiting." However, this message is not showing in production. In addition we see the following failure information in the job yaml from the production pod for the job:
type: Failed status: 'True' lastProbeTime: '2023-03-16T03:30:00Z' lastTransitionTime: '2023-03-16T03:30:00Z' reason: DeadlineExceeded message: Job was active longer than specified deadline
This means that our database is growing in size and we are not properly cleaning up old information. The customer impact is that queries will slow down over time degrading performance.
Pull in QE on any implementation cards.
- relates to
-
SWATCH-1148 Curl based tally snapshot purge job is failing with 403 response
- Closed