5 Commits

Author	SHA1	Message	Date
Luiz Aoqui	b1753d0568	scheduler: detect and log unexpected scheduling collisions (#11793)	2022-01-14 20:09:14 -05:00
Mahmood Ali	e06ff1d613	scheduler: stop allocs in unrelated nodes (#11391) ... The system scheduler should leave allocs on draining nodes as-is, but stop node stop allocs on nodes that are no longer part of the job datacenters. Previously, the scheduler did not make the distinction and left system job allocs intact if they are already running. I've added a failing test first, which you can see in https://app.circleci.com/jobs/github/hashicorp/nomad/179661 . Fixes https://github.com/hashicorp/nomad/issues/11373	2021-10-27 07:04:13 -07:00
Luiz Aoqui	a553063c92	test: use Len instead of Equal on system and sysbatch node constraint tests	2021-09-02 11:36:02 -04:00
Luiz Aoqui	3cbf75a5e7	tests: update expected test result based on changes done in #11111	2021-09-01 19:49:04 -04:00
Seth Hoenig	3371214431	core: implement system batch scheduler ... This PR implements a new "System Batch" scheduler type. Jobs can make use of this new scheduler by setting their type to 'sysbatch'. Like the name implies, sysbatch can be thought of as a hybrid between system and batch jobs - it is for running short lived jobs intended to run on every compatible node in the cluster. As with batch jobs, sysbatch jobs can also be periodic and/or parameterized dispatch jobs. A sysbatch job is considered complete when it has been run on all compatible nodes until reaching a terminal state (success or failed on retries). Feasibility and preemption are governed the same as with system jobs. In this PR, the update stanza is not yet supported. The update stanza is sill limited in functionality for the underlying system scheduler, and is not useful yet for sysbatch jobs. Further work in #4740 will improve support for the update stanza and deployments. Closes #2527	2021-08-03 10:30:47 -04:00

Renamed from scheduler/system_sched_test.go (Browse further)