Describe this problem
CeresMeta node need to create grpc client in the following two scenarios:
Forward request to CeresMeta leader node, the leader node address is http format like http://127.0.0.1:22380.
Dispatch event to CeresDB node, CeresDB node address is endpoint with port like 127.0.0.1:2379.
But CeresMeta current only support the second scenario, when forward request to leader node, the following error occurs:
ERRO [cluster/src/cluster_impl.rs:80] Send heartbeat to meta failed, err:Failed to send heartbeat, cluster:defaultCluster, err:status: Unavailable, message: "connection error: desc = \"transport: Error while dialing dial tcp: address http://127.0.0.1:22379: too many colons in address\"", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc"} }
Steps to reproduce
Start CeresMeta and CeresDB in cluster mode.
Close CeresMeta leader node.
Expected behavior
CeresMeta node can create grpc client in both cases.
Describe this problem CeresMeta node need to create grpc client in the following two scenarios:
http://127.0.0.1:22380.127.0.0.1:2379.But CeresMeta current only support the second scenario, when forward request to leader node, the following error occurs:
ERRO [cluster/src/cluster_impl.rs:80] Send heartbeat to meta failed, err:Failed to send heartbeat, cluster:defaultCluster, err:status: Unavailable, message: "connection error: desc = \"transport: Error while dialing dial tcp: address http://127.0.0.1:22379: too many colons in address\"", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc"} }Steps to reproduce
Expected behavior CeresMeta node can create grpc client in both cases.
Additional Information