Nomad, a cluster manager and scheduler
>Nomad is designed to be a global state, optimistically concurrent scheduler. Global state means schedulers get access to the entire state of the cluster when making decisions enabling richer constraints, job priorities, resource preemption, and faster placements.Can anyone shed light on how that's possible? I was under the impression that global state in distributed systems was not possible?