We had set the spread algorithm to be the default algorithm within the nomad server configuration. This was working up till we upgraded from 1.3.6 to 1.5.3. When I query the server for its scheduling config I get the expected response
{"SchedulerConfig":{"SchedulerAlgorithm":"spread","PreemptionConfig":{"SystemSchedulerEnabled":false,"SysBatchSchedulerEnabled":false,"BatchSchedulerEnabled":false,"ServiceSchedulerEnabled":false},"MemoryOversubscriptionEnabled":false,"RejectJobRegistration":false,"PauseEvalBroker":false,"CreateIndex":5,"ModifyIndex":1074704},"Index":1074704,"LastContact":0,"KnownLeader":true,"NextToken":""}%
When I then check an allocations placement metrics I can see binpack is still being used
| Node | binpack | job-anti-affinity | node-reschedule-penalty | final score |
|--------------------------------------|---------|-------------------|-------------------------|-------------|
| 82273c80-f2f7-3aa9-f4ae-def7966d619b | 0.442 | 0 | 0 | 0.422 |
Am I missing something because I don’t see anything in the release logs other than a bug fix in regards scheduling -inf.
Thanks.