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 seem to be encountering a race condition related to configuration reloading when refresh_interval is set to the catalog default of 10 seconds.
Test Configuration
I'm testing in a Rancher environment with three hosts. Each host is running one instance of rawmind/alpine-traefik:1.1.2-1. I am automating deployments to this environment from GitLab which often results in multiple stacks being created/destroyed in a very short period of time.
Traefik acts as if no configuration change has occurred. About a third of my deployments and up being unreachable (traefik responds with a 404 error) until I upgrade the Traefik services to force a reload.
What I've tried
I've had success in changing the refresh_interval to be less frequent. With a setting of 60 seconds I have not had a single occurrence of this issue so far.
The text was updated successfully, but these errors were encountered:
After digging into this a bit more it's clear that the rules.toml file is being updated correctly, so any issue must be an upstream issue with traefik itself.
I seem to be encountering a race condition related to configuration reloading when
refresh_interval
is set to the catalog default of 10 seconds.Test Configuration
I'm testing in a Rancher environment with three hosts. Each host is running one instance of
rawmind/alpine-traefik:1.1.2-1
. I am automating deployments to this environment from GitLab which often results in multiple stacks being created/destroyed in a very short period of time.docker-compose.yml
Symptoms
Traefik acts as if no configuration change has occurred. About a third of my deployments and up being unreachable (traefik responds with a 404 error) until I upgrade the Traefik services to force a reload.
What I've tried
I've had success in changing the
refresh_interval
to be less frequent. With a setting of 60 seconds I have not had a single occurrence of this issue so far.The text was updated successfully, but these errors were encountered: