Incorrect peer_addr in cluster_info meta table about greptimedb HOT 5 CLOSED

I think gRPC port is good because it exists in all three types of nodes. Other protocols such as HTTP does not.

from greptimedb.

Also we should not show grpc port here because on these three node types, grpc serves different purpose and its
meaningless to list them together.

But in another meaning, they are serving the same purpose - gRPC requests, wherever they come from users or internal requests.

from greptimedb.

The metasrv address is correct. It uses server_addr in metasrv configuration,which is the the communication server address for frontend and datanode to connect.

from greptimedb.

But in another meaning, they are serving the same purpose - gRPC requests, wherever they come from users or internal requests.

One scenario I realized using port here may make sense is when multiple instances deployed on a single node, we use port as some sort of process id. I'm ok to keep it until we find better alternatives. We still need to explain the meaning of the ports when it's listed on cluster topology view.

from greptimedb.

We can add a node_info table to list all the binding ports for a node.

from greptimedb.