You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I backup the default database, which consists of one collection, everything goes well (milvus-backup create -d deafault --config configs.yaml).
When I backup another database of more than 2500 collections, I get an error (milvus-backup create -d rag_platform_mvp --config configs.yaml)
The same thing if I backup all the databases together (milvus-backup create --config configs.yaml).
It looks like the issue is caused by a gRPC connection being interrupted. Could you please check if there is a load balancer (LB) between the backup tool and Milvus? If so, does the LB have any limitations on response size or connection duration?
Since the database contains more than 2500 collections, the metadata response from Milvus could be quite large, which may trigger such limitations.
Current Behavior
Milvus 2.4.10
milvus-backup 0.5.3
When I backup the default database, which consists of one collection, everything goes well (milvus-backup create -d deafault --config configs.yaml).
When I backup another database of more than 2500 collections, I get an error (milvus-backup create -d rag_platform_mvp --config configs.yaml)
The same thing if I backup all the databases together (milvus-backup create --config configs.yaml).
Expected Behavior
No response
Steps To Reproduce
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: