start-os
start-os copied to clipboard
Limit number of simultaneous installs
Either solve issues surrounding large number of simultaneous installs, or create a queue and limit them
This also ought to apply to the installation of recovered services
Causes same issue as quoted in #905
Reported by: @kn0wmad
What is "a large number of installs", and what "bugs" are you seeing?
This was discussed internally. I noticed with 5-6 simultaneous installs and it causes failed installs and "hanging" (perceived, not permanent). It's just a bad UX. I personally think the solution is to just limit simultaneous installs to 3 (for now), but I don't know how difficult this is. This is pretty common on any popular marketplace or app.
I might suggest limiting simultaneous installs to 4 or something. Should be easy to implement with a semaphore or something @dr-bonez
kicking from 0.3.0 SoW
Rebuilding a box and wanted to mention that multiple installs (3-4) while doing docker actions (configure) caused a crash. Bitcoin was also 'catching up' from 99.89% at this time. Reproduced once after reboot. Reboot is the solution. This is easy enough to support to remain punted
If the backup is done one by one, recovery should be like that as well.
Example picture:

If the backup is done one by one, recovery should be like that as well.
This is an issue primarily with fresh installs. Not with the overall backup restoration process. We have to put some upper bound on simultaneous installs so we don't hurt reliability.
People will probably hit this bug a lot when migrating from 02x, and probably very rarely otherwise
bumping this thread - migrating to 0.3.1 with all the service updates makes this prominent
Will be fixed by removing db locks #2052