The scheduler is able to start the creation of a backup while another backup is still running. This creates a loop of backups which can cause an entire node to crash.
I've experienced this multiple times.
Expected Behavior
Don't start multiple backup processes.
It shouldn't ignore the user limits (like disk size limit)
Actual Behavior
It completely fills the disk (even when the user has a 20GB backup limit). So it ignores the user limits. Because it starts creating a lot of backups this also causes full cpu utilization on the node. Even when the user has a limit of 200%.
Describe the bug
The scheduler is able to start the creation of a backup while another backup is still running. This creates a loop of backups which can cause an entire node to crash. I've experienced this multiple times.
Expected Behavior
Don't start multiple backup processes. It shouldn't ignore the user limits (like disk size limit)
Actual Behavior
It completely fills the disk (even when the user has a 20GB backup limit). So it ignores the user limits. Because it starts creating a lot of backups this also causes full cpu utilization on the node. Even when the user has a limit of 200%.
Disk usage (node)
A lot of backups are running at the same time
Steps to Reproduce
Create a schedule like this:
It should create a backup every minute.
Browser Details
Chrome
Operating System
Windows 10
Optional additional information
Have fun crashing hosts using Wisp!