[FEATURE]: When connect to cluster failed, the error message is confusing

[xiaofan-luan]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe.

see milvus-io/milvus#28076

When we connect to the wrong port, you will still get GRPC unimplemented error and the error message of upgrade pymilvus version is a little confusing

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Anything else?

No response

[jfgrea27]

Hi @xiaofan-luan, happy to be assigned this one. Mind assigning me?

[jfgrea27]

Have you been able to replicate the bug (=confusing log line)?

With the Docker Standalone running on port 19530 and the following

from pymilvus import MilvusClient

client = MilvusClient(
    uri="http://localhost:19531"
)

The following exception is raised after a timeout:

    raise MilvusException(
pymilvus.exceptions.MilvusException: <MilvusException: (code=2, message=Fail connecting to server on localhost:19531, illegal connection params or server unavailable)>

I believe this error is not confusing as it says the server at port 19531 is not available (which is true as it is on 19530).

The OP is pretty old; the error log from OP might have been resolved during the fix of `1455 - although this is older than the OP..