Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.
I am currently utilizing Consul version 1.10.3 in conjunction with various microservices built on .NET Core. Occasionally, I encounter an issue where a service deregisters abruptly and then re-registers itself. During these instances of service deregistration, I execute connectivity and probe health check commands between the microservices and Consul, and they appear to be functioning correctly. Is there a configuration setting within the config.json file that dictates the duration of service deregistration?
@kkarim1983 Would you be able to provide a bit more information on how you are registering these services to Consul? Are there any messages in the logs that indicate why the service is being deregistered?
I am currently utilizing Consul version 1.10.3 in conjunction with various microservices built on .NET Core. Occasionally, I encounter an issue where a service deregisters abruptly and then re-registers itself. During these instances of service deregistration, I execute connectivity and probe health check commands between the microservices and Consul, and they appear to be functioning correctly. Is there a configuration setting within the config.json file that dictates the duration of service deregistration?