-
Notifications
You must be signed in to change notification settings - Fork 50
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
[Bug]: No binlog on backup #183
Comments
@jackfischer milvus-backup/core/backup_impl_create_backup.go Lines 595 to 597 in 9afbc4e
The backup works by finding the file path of the original segment and copying it to the backup path. The problem is that the file path of the segment is not found. By the way, you can also attach the debug log here for more detailed info. You can get it by setting log level to debug milvus-backup/configs/backup.yaml Line 3 in 9afbc4e
|
We do indeed get insert logs, here is a sample of the output,
And attaching debug level log, |
/assign @wayblink |
@jackfischer |
Hey we're on |
@jackfischer We found a bug about config, your case may also caused by this. Please use the latest 0.3.3 version. |
Unfortunately same effect on f2515c9 0.3.3. Were there any other steps I need to take?
|
@jackfischer Hi, seems the log is not complete or the backup progress is not done. meta file generate in the end, after all data is copied. Did you terminate the progress manually? Please wait to end and see the result |
Thanks you. That is the normal end of the log file. Waited for it to finish, did not kill the process or anything like that. |
Well, that it quite strange. I have no idea what happened. The log shows backup working good. It should be some error or panic if it failed... |
1 similar comment
Well, that it quite strange. I have no idea what happened. The log shows backup working good. It should be some error or panic if it failed... |
What other info can we provide? I can audit the JSON files that do land for proprietary information and send those over? Helpful to get on a screen share? |
@jackfischer hi, I think it is an issue about empty rootPath. please try revert this pr #177 and retry |
hello, |
I think it is related to the storage system you use. What is your storage system. |
Hi, i resolved this issue by using minio command to sync the back to the local, instead of using "cp" command. |
Current Behavior
Perform backup but only metadata persisted.
Expected Behavior
Expect binlogs to be persisted in the backup.
Steps To Reproduce
Run a normal backup with bucket name and
rootPath: ""
and receive only metadata persisted.Files are present in S3, as recommended to check in milvus-io/milvus#26088
Only the following files are written
Environment
No response
Anything else?
This is mentioned as a possibility in two places, #47 in which it's suggested this should be treated as a failure, with one comment saying they are experiencing this behavior, and milvus-io/milvus#26088 , false positive due to typo in
rootPath
(milvus_files
vsmilvus-files
) but this is not the case for us.The text was updated successfully, but these errors were encountered: