Closed jackfischer closed 1 month ago
@jackfischer
When you run aws s3 ls s3://credal-milvus --recursive
, and grep with segment id 443242844026507367
, can you see insert_log in the output?
https://github.com/zilliztech/milvus-backup/blob/9afbc4ea1890b0ab9770364aea894fbdfbee2676/core/backup_impl_create_backup.go#L595-L597 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 https://github.com/zilliztech/milvus-backup/blob/9afbc4ea1890b0ab9770364aea894fbdfbee2676/configs/backup.yaml#L3
We do indeed get insert logs, here is a sample of the output,
2023-08-21 11:37:55 44662021 insert_log/442270139975731376/442270139975731377/443242844026507367/110/443242844026507728
2023-08-21 11:37:58 33396311 insert_log/442270139975731376/442270139975731377/443242844026507367/110/443242844026507762
2023-08-21 11:37:11 588426 insert_log/442270139975731376/442270139975731377/443242844026507367/111/443242844026507400
2023-08-21 11:37:19 655322 insert_log/442270139975731376/442270139975731377/443242844026507367/111/443242844026507456
2023-08-21 11:37:25 730703 insert_log/442270139975731376/442270139975731377/443242844026507367/111/443242844026507501
And attaching debug level log, debug.log
/assign @wayblink PTAL
@jackfischer Thanks for your feedback. Not sure which version of the backup tool you are using. Can you try with the latest milvus-backup? It fixes some bugs about empty rootPath.
Hey we're on 9afbc4ea1890b0ab9770364aea894fbdfbee2676
, just beyond the latest, 0.3.2.
@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 f2515c9e1 0.3.3. Were there any other steps I need to take?
git pull
go build
@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.
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...
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...
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, have reverted #177 on top of #200 but have the same result. Logs attached. To confirm, this is correct to test?
go build && ./milvus-backup create -n prod11sep_4
hello,
is there anyone resolve this issue? it seems the same as on my side, after creating a backup the content looks like:
meta/backup_meta.json/xl.meta
i was expecting there should be only meta/backup_meta.json file.
hello, is there anyone resolve this issue? it seems the same as on my side, after creating a backup the content looks like:
meta/backup_meta.json/xl.meta
i was expecting there should be only meta/backup_meta.json file.
I think it is related to the storage system you use. What is your storage system.
hello, is there anyone resolve this issue? it seems the same as on my side, after creating a backup the content looks like:
meta/backup_meta.json/xl.meta
i was expecting there should be only meta/backup_meta.json file.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 https://github.com/milvus-io/milvus/issues/26088
Only the following files are written
Environment
No response
Anything else?
This is mentioned as a possibility in two places, https://github.com/zilliztech/milvus-backup/issues/47 in which it's suggested this should be treated as a failure, with one comment saying they are experiencing this behavior, and https://github.com/milvus-io/milvus/issues/26088 , false positive due to typo in
rootPath
(milvus_files
vsmilvus-files
) but this is not the case for us.