-
Notifications
You must be signed in to change notification settings - Fork 49
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
Error at restart with a high number of services #1315
Comments
I suspect this is all triggered by the services starting together and overloading the API of the core service. We have done the first state of adding the ability to order the start up, which will help with this. But we need to probably complete that work south that we can stagger the startup of the south services. Or maybe even have a mechanism that automatically rate limits the service startup when we start getting large numbers. |
I tried with just one south service configured and when I stop then restart fledge I get more than 300 hundreds http requests across all services just for them to restart (there is non data acquisition). I excluded ping http requests.
|
@MarkRiddoch I found the issue. Simple-Web-Server has a default request timeout of 5s: |
A new configuration item has been added to the Advanced - Storage category that allows this timeout to be set. The default has also been increased. This is in the develop branch and will be in tonights nightly build. |
I have 150 south services and 10 north services and when I stop then start fledge I have the following error:
I also have sometimes this kind of crash:
Any idea what could be the issue and if there is a way to workaround ?
The text was updated successfully, but these errors were encountered: