use dapr_scheduler.ha to allow for scaling independently of the global.ha#8304
Conversation
…al.ha Signed-off-by: Cassandra Coyle <[email protected]>
There was a problem hiding this comment.
I think we should also support the case when global HA is true and scheduler HA is false. For comparison, placement will allow HA when its own local HA is true, and the global is false.
Otherwise, lgtm.
EDIT: Nevermind, I checked with placement, and it behaves the same way
Hey @elena-kolevska! Thanks for the review! re: your comment: Are you saying you want the local scheduler flag to override the global ha flag specifically for the case where re: your comment: |
Signed-off-by: Cassandra Coyle <[email protected]>
|
Yeah, nevermind, I had commented relying just on the comment in the helm file itself without reading the PR comment, the behaviour is fully consistent with placement! |
…l.ha (dapr#8304) * allow for local dapr_scheduler.ha to be used to scale outside of global.ha Signed-off-by: Cassandra Coyle <[email protected]> * update code comment local ha -> dapr_scheduler.ha for readability Signed-off-by: Cassandra Coyle <[email protected]> --------- Signed-off-by: Cassandra Coyle <[email protected]> Signed-off-by: Jake Engelberg <[email protected]>
allow the use of
dapr_scheduler.hato scale independely of the global ha flag. This allows for global ha to be false and to scale the schedulers to 3 instances.I confirmed the following to be true by testing all cases locally.
High level (flag breakdown):
--set global.ha.enabled=trueneither--set dapr_scheduler.ha=false --set dapr_placement.ha=falseare respected meaning you are unable to be globally ha and have either of the placement or scheduler as a single instance. global being true overrides local being false (bc it defaults to false)--set dapr_scheduler.ha=true