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
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!
The text was updated successfully, but these errors were encountered:
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.
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!
The text was updated successfully, but these errors were encountered: