Lifecycle Conductor Cron Is Working too Fast¶

Problem Description¶

By default, a bucket scan is initiated every 12 hours. A problem occurs when there are few buckets with a large number of objects. The object processor lists the same range of buckets at the same time and tries to delete the objects multiple times at once.

The following issues are noticed:

Several 404 errors in the object processor logs as it tries to delete already deleted objects, or in S3 service dashboard.
An increasing lag of the object processor topic due to the errors.

Problem Resolution¶

Important

Do not perform this procedure if Lifecycle Transition is enabled.

Configure the cron rule in Zenko CR.

[artesca-os@bootstrap ~]$

sudo kubectl --kubeconfig /etc/kubernetes/admin.conf edit zenko artesca-data -n zenko

In the Spec section, add a new backbeat entry or edit it if it already exists.
```
backbeat:
  lifecycleConductor:
    cronRule: '0 */1 * * *'
```

Set the cron rule according to your configuration. For example, if you only have one bucket, make sure the rule matches the time it takes to process all the bucket’s objects.

┌──────────── minute (0 - 59)
│ ┌────────── hour (0 - 23)
│ │ ┌──────── day of the month (1 - 31)
│ │ │ ┌────── month (1 - 12)
│ │ │ │ ┌──── day of the week (0 - 6) (0 and 7 both represent Sunday)
* * * * *