You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
@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?
The text was updated successfully, but these errors were encountered: