Consul cluster data synchronization problem

[blake]

This post should provide a better explanation of how service registration works against agents and how that data is aggregated in the service catalog by the servers.

What is the different between /catalog/service and /agent/service/?

Hi @cheyuxuanll, Consul is designed for services to be registered against a Consul client agent which is running on the same host where a service is deployed. The /v1/agent/service/ endpoints provide a way for you to interact with services which are registered with the specific Consul agent to which you are communicating, and register new services against that agent. Each Consul agent in the data center submits its registered service information to the Consul servers. The servers aggregate thi…

@Wangyxiang

Normally, the client node will synchronize the service registration information on itself to the server node, but it doesn’t seem to happen on my side. Is there something wrong with my configuration?

If you query $CONSUL_HTTP_ADDR/v1/catalog/services, are you seeing all of your service names returned in the output? If so, the services are being successfully aggregated in the server’s service catalog.