Open CSi-CJ opened 4 months ago
The retry machinery is consistent with the milvus python sdk which is as-designed: https://github.com/milvus-io/pymilvus/blob/1081c49fcc21039300fec22e7b19805be8f198f0/pymilvus/decorators.py#L42
The loadCollection() calls showCollection() to check loading progress. Seems the showCollection() failed in rpc.
"CANCELLED: Failed to read message" is a GRPC error, it indicates the connection is broken or closed.
Yeah, it seems like grpc connection has crashed. I launched the Milvus standalone cluster in the local Ubuntu environment, the infra is as below:
I almost found the problem where is, cause my Milvus helm chart installs failed, and the query-node pod has not been found. I think maybe reinstalling the Milvus cluster can work normally. please help me confirm whether the cluster status is correct
The querycoord failed to initialize. Need the full log to know what the error is.
Problem Description
When calling the
![image](https://github.com/milvus-io/milvus-sdk-java/assets/57539387/9bebd675-0316-462d-ab3f-e60157f3508c)
loadCollection
method after creating a collection withmilvus-sdk-java
2.4.0, theMilvusServiceClient
keeps executing a loading loop and throwing errors. Weirdly,milvus-attu
shows that the collection has been loaded, but the console log keeps looping with errors.Error Log
Environment
Steps to Reproduce
Expected Behavior
The collection should be loaded successfully without looping errors.
Additional Information
Hope someone can help me resolve this issue.
Additionally, I noticed that the
MilvusServiceClient
has a default retry mechanism for almost every database interaction withprivate int maxRetryTimes = 75
. Why is the retry count set to 75? Is there any specific reason behind this number?