This repository has been archived by the owner on Jun 20, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 670
DNS records disappear after a few hours #1177
Comments
This issue can now be reproduced automatically by running setup.sh (from the ECS guide). You still need to wait for the records to disappear though. |
I've had master running over the weekend (not using the ecs stuff, using the 210 test), and the entries were still there this morning. I'm going to add a http handler to retrieve entries (including tombstones) and then try and reproduce with ecs scripts. |
Okay I've spun up a new cluster based off the 1177-dns-disappear branch, with the new http handler:
I will now leave this for a day. |
rade
added a commit
that referenced
this issue
Jul 20, 2015
Don't periodically delete all non-tombstone entries. Fixes #1177.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If I let the example of the (still unfinished) ECS guide running for a few hours, DNS records disappear and are not resolvable.
The setup consists of 3 hosts with 3 containers each, which register the same DNS records in all the hosts:
ecs-agent
(Amazon's ECS Agent container)dataproducer
httpserver
Here are the logs and status of one of the hosts and here's what I do to confirm the problem:
The commands above work for at least one hour after spawning the instances.
I am using weave/master with some extra proxy fixes on top which I need for
ecs-agent
to work withweave
.The text was updated successfully, but these errors were encountered: