Report a Dgraph Bug
The issue arose incremental backups were made without a full backup.
What version of Dgraph are you using?
Have you tried reproducing the issue with the latest release?
What is the hardware spec (RAM, OS)?
- Amazon Linux EKS nodes with Dgraph Ubuntu containers
Steps to reproduce the issue (command/config used to run Dgraph).
At this moment, still researching the steps to reproduce this issue, but deducing one probable way this can occur is the following:
- Do backups simultaneously on two different alpha nodes, e.g.
- Use the same backup destination for all backups, e.g. s3 bucket or NFS mount.
Expected behavior and actual result.
A summary is a situation is that there is an assumption that after you start a new backup, all the backups after that belong to the same series of backups until a new full backup is forced. If this assumption is broken, when we can get into this scenario.
As a workaround, we can use two different folders for each of the backup series and make sure we only execute a backup on the same alpha node if they occur concurrently.