Repository navigation
Release v1.30.0
Hosts can now choose where job controllers and job-step workers are placed, separately and without changing any job or step class. Nothing changes for hosts that do not opt in.
Added
AddJobPlacement()/AddJobPlacement<TDirector>()andAddJobStepPlacement()/AddJobStepPlacement<TDirector>()silo builder extensions opt in to the newJobsPlacementStrategy(job controllers) andJobStepsPlacementStrategy(job-step workers). Without a host director, the default directors place controllers with resource-optimized placement and steps with the cluster default, exactly as before. Recovered steps go through the worker strategy. Enable either strategy only once every silo in the cluster runs this version, and register it identically on every silo. (part of #129)NoEligibleJobWorker, which a host placement director throws when no silo may host a job grain. Orleans does not retry it; the job's existing failure handling applies. (part of #129)UseJobStepParallelismFromSiloMetadata()sizes the job-step throttle per silo from the silo's metadata, falling back toJobsOptions.MaxParallelSteps. (part of #129)