cloudnative-pg / cloudnative-pg/klio

No backup capability on immediate backup from replica cluster

Open
#268 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
26
Forks
5
Avg merge
1d 11h
Merged PRs (30d)
113

Description

When starting a replica cluster together with a scheduledbackup that has `immediate`, the backup starts when the Klio sidecar is the restore one, and not the standard one. This means that the immediate backup will fail, because the `klio-restore` sidecar has no backup capability.

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by tracing how an immediate scheduledbackup is dispatched when a replica cluster starts, focusing on which Klio sidecar is selected. Reproduce the case and confirm that the standard sidecar, rather than klio-restore, performs the backup successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.