0181a1b5b1
A repair is a sync scan that acts only on those clusters that indicate that the last add, update or sync operation on them has failed. It is supposed to kick in more frequently than the repair scan. The repair scan still remains to be useful to fix the consequences of external actions (i.e. someone deletes a postgres-related service by mistake) unbeknownst to the operator. The repair scan is controlled by the new repair_period parameter in the operator configuration. It has to be at least 2 times more frequent than a sync scan to have any effect (a normal sync scan will update both last synced and last repaired attributes of the controller, since repair is just a sync underneath). A repair scan could be queued for a cluster that is already being synced if the sync period exceeds the interval between repairs. In that case a repair event will be discarded once the corresponding worker finds out that the cluster is not failing anymore. Review by @zerg-junior |
||
|---|---|---|
| .. | ||
| cluster.go | ||
| cluster_test.go | ||
| exec.go | ||
| filesystems.go | ||
| k8sres.go | ||
| k8sres_test.go | ||
| pg.go | ||
| pod.go | ||
| resources.go | ||
| sync.go | ||
| types.go | ||
| util.go | ||
| volumes.go | ||