Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start Listeners After Routing Table Initialized #756

Open
codyja opened this issue Mar 10, 2020 · 2 comments
Open

Start Listeners After Routing Table Initialized #756

codyja opened this issue Mar 10, 2020 · 2 comments

Comments

@codyja
Copy link

codyja commented Mar 10, 2020

Hi, I noticed that fabio will start it's listeners, begin passing health checks, and start receiving inbound traffic before the route table is finished initializing. This causes a lot of 404 errors since routes aren't found. This is especially noticable in networks with about 7-8k routes due to how long the route table initialization takes. I also found this related issue that was closed out. #248

An alternative would be to have an endpoint that we can do a health check against to confirm route table has been initialized.

Thanks!

@codyja
Copy link
Author

codyja commented Mar 12, 2020

It looks like the "manual" routes (which we don't really use) loads first and so the listeners go active before the full list of services comes back from Consul services.

@ketzacoatl
Copy link

I agree that it would be really nice to have fabio finish the route initialization before receiving inbound traffic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants