Services with TTL expired not cleared

783 views
Skip to first unread message

George Chilumbu

unread,
Dec 27, 2015, 9:44:51 AM12/27/15
to Consul
I have some services that i have deleted and not using anymore, but yet they still exist in the web ui as "TTL expired" and reporting as critical. The deleted service was on a node where another service is which is still running fine. But because of the removed service with expired TTL, the IP/port of this node is not being listed when a DNS is queried.

How can i clear this expired TTL from this node so that the only service being shown is the one that is still available and is running with passing?

Armon Dadgar

unread,
Dec 27, 2015, 5:10:46 PM12/27/15
to consu...@googlegroups.com, George Chilumbu
Hey George,

Consul uses health checks to restrict if a service instance is returned as part
of a DNS result or API response (depending on health filtering settings). However,
it does not automatically deregister services for you. Its entirely unclear to Consul if
the service is down temporarily or permanently, so it errs on the side of caution.

If this is behavior you want, you can leverage the existing API to deregister services
once they’ve been failed for long enough or based on some other criteria. 

Hope that helps!

Best Regards,
Armon Dadgar

On December 27, 2015 at 6:44:54 AM, George Chilumbu (chilumb...@gmail.com) wrote:

I have some services that i have deleted and not using anymore, but yet they still exist in the web ui as "TTL expired" and reporting as critical. The deleted service was on a node where another service is which is still running fine. But because of the removed service with expired TTL, the IP/port of this node is not being listed when a DNS is queried.

How can i clear this expired TTL from this node so that the only service being shown is the one that is still available and is running with passing?

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/consul/issues
IRC: #consul on Freenode
---
You received this message because you are subscribed to the Google Groups "Consul" group.
To unsubscribe from this group and stop receiving emails from it, send an email to consul-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/consul-tool/b59751a1-ce7e-47d4-aaa6-51b2276f25cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

George Chilumbu

unread,
Dec 29, 2015, 11:41:46 AM12/29/15
to Consul, chilumb...@gmail.com
Hi Armon,

I was able to manually deregister the failed services.

But now i have a different situation where in web ui, the same node is listed twice in a duplicate fashion. In the first listing, it shows that a health check of a service and serf are being checked. In the second listing of the node, only serf is being checked. All checks in both listings of the node are passing. The second lasting as pointed out does not have a check for any services. 

How can i remove the second listing so i have only one node listed with the check on a service and serf?

George Chilumbu

unread,
Dec 29, 2015, 11:43:14 AM12/29/15
to Consul, chilumb...@gmail.com
By the way i tried consul force-leave node but it does not work. The duplicate node is still there.


On Monday, December 28, 2015 at 6:10:46 AM UTC+8, Armon Dadgar wrote:

Armon Dadgar

unread,
Dec 29, 2015, 2:10:41 PM12/29/15
to consu...@googlegroups.com, George Chilumbu, chilumb...@gmail.com
George,

The node likely has a different node name, as Consul indexes by that.
You can use the “/v1/catalog/deregister” API to force deregistration of the node.

Hope that helps!

Best Regards,
Armon Dadgar

Message has been deleted

Armon Dadgar

unread,
Jan 3, 2016, 2:36:00 PM1/3/16
to consu...@googlegroups.com, George Chilumbu, chilumb...@gmail.com
George,

That is certainly bizarre… Can you get the output of “curl http://localhost:8500/v1/health/service/redis?pretty=1”.
I’m not sure how thats possible, it may be a UI bug or something.

Best Regards,
Armon Dadgar

On December 29, 2015 at 6:21:45 PM, George Chilumbu (chilumb...@gmail.com) wrote:

Hi Armon,

The node name is actually the same. And when i try to deregister nothing happens. Below is a screenshot of the web ui:

Reply all
Reply to author
Forward
0 new messages