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
Describe the bug
The Milvus() will wait for 90 seconds if milvus server is not running. The Milvus() call to ping(), the ping() has a parameter "timeout=30", and the GrpcHandler has a member "max_retry", its default value is 3. After 90 seconds, the Milvus() will raise an exception "Fail connecting to server on xxx. Timeout"
This behavior is not friendly to users. Maybe the Milvus() should provide a "timeout" parameter.
Expected behavior
Set timeout for Milvus() so we can write code like this:
Describe the bug
The Milvus() will wait for 90 seconds if milvus server is not running. The Milvus() call to ping(), the ping() has a parameter "timeout=30", and the GrpcHandler has a member "max_retry", its default value is 3. After 90 seconds, the Milvus() will raise an exception "Fail connecting to server on xxx. Timeout"
This behavior is not friendly to users. Maybe the Milvus() should provide a "timeout" parameter.
Expected behavior
Set timeout for Milvus() so we can write code like this:
Comment
This issue makes users hard to apply pymilvus in production.
The text was updated successfully, but these errors were encountered: