Bug #8405
Updated by Evgeny Novikov over 6 years ago
Indeed it For instance, I have a job with a low priority but which requires 300 GB of a disk space. Then I started one more job with an urgent priority which requires 100 GB of a disk space. There is only 396 GB of a bit complicated task disk space in total. Native Scheduler seems to catch corresponding errors. kill the first job and tries to decide the second one. This isn't an expected behavior. I don't treat this issue as a critical bug or a regression since it was likely introduced during recent schedulers refactoring.