Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Effect of backup on currently indexing collection #464

Open
nisharyan opened this issue Nov 20, 2024 · 1 comment
Open

Effect of backup on currently indexing collection #464

nisharyan opened this issue Nov 20, 2024 · 1 comment

Comments

@nisharyan
Copy link

Documentation Link

No response

Describe the problem

The documentation says

The Milvus-backup process has negligible impact on the performance of Milvus. Milvus cluster is fully functional and can operate normally while backup and restoration are in progress.

Need further clarification on how the in-progress indexing data is handled?
There are two use-cases I can think of:

  • A new collection is created and being indexed during the backup.
  • Updates are made to an existing collection during backup.

Does it backup this data as well? How does the backup tool handle these scenarios?

Describe the improvement

No response

Anything else?

No response

@zhuwenxing
Copy link
Collaborator

A new collection is created and being indexed during the backup

During backup, the backup tool does not back up indexes. Indexes are rebuilt during recovery.

Updates are made to an existing collection during backup

When the backup is triggered, there will be a current timestamp (ts). Only data before this ts will be backed up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants