swiftwave: bug: ingress stuck in pending/deleting
Describe the bug
First time user of SwiftWave here. Trying it out on a Debian 12 VM in the local network. Installation was quick and flawless.
I have now created a new app running Wordpress with MariaDB from the App Store. I figured that my ingress would not work properly so I tried to remove it and create a new one with the proper FQDN. However the old ingress is not removed after several minutes and the new one is still pending:
The server’s log shows:
2024/08/20 10:53:21 error while invoking function for queue [ingress_rule_apply]
POST /graphql | 10.6.56.60 | 200
POST /graphql | 10.6.56.60 | 200
POST /graphql | 10.6.56.60 | 200
2024/08/20 10:53:25 error while invoking function for queue [ingress_rule_delete]
Are you working on this issue?
No
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 27 (10 by maintainers)
@HWiese1980 The issue is with docker swarm. It has no mechanism to report back the status on some change. Swiftwave poll it on a fixed interval, but what happens that we will get running in most of the case.
Because, every time the container fails to start , swarm service try to start again a new one. Polling it every second might work, but that will put lot of pressure on the server (cadvisor has same issue with large servers with constant polling https://github.com/google/cadvisor/issues/2459).
Without proper integration with
docker deamon event stream, it’s tough to tackle.Most of the time, this issue doesn’t appear because, people are doing this on a fresh instance.
In v3.0, doing the integration with 1 level deeper and will not require swarm even. Hoping all these issues will be solved.
Thanks for the swift response, @tanmoysrt.
It seems I had not:
Enabling ingress proxy as “Active”…
The ingresses went into “Failed” and after waiting 1-2 minutes, they are now gone.
Thanks. Continuing my journey.