shinyproxy Repeated container failures on ShinyProxy startup

This is related to the uptime monitoring thread: https://github.com/openanalytics/shinyproxy/issues/517 As well as the restarter thread: https://github.com/openanalytics/shinyproxy/issues/510

I implemented a rudimentary monitoring solution, which searches the logs and finds when a Delegate fails to start, then sends an email.

One thing that I have noticed is that when I restart ShinyProxy in our test environment and in production with a larger memory and more CPU the containers often fail repeatedly to start, likely due to competition for resources.

These apps don't typically take five or ten tries to launch after a new user connects, the new container comes up with only the normal docker mesh delay.

Is there any way to serialize or stagger the launches?

Oct 15 '24 16:10 kramerrs

Just add some more info. I can reduce the number of startup failures by increasing the container-wait-time, though this is very long.

container-wait-time: 1200000

Oct 16 '24 13:10 kramerrs

Hi, this is currently not possible, but I do see the need for this. I created an internal ticket for it.

Oct 28 '24 14:10 LEDfan