We've made internal changes to how background processing work is distributed across nodes in high-availability environments for self-hosted versions of Octopus Server.
Some background processing that previously ran on all node's will now run only on nodes configured to execute tasks where the configured Task Cap is greater than 0.
What this means for you:
- If all of your nodes are configured with a Task Cap greater than 0, there will be no change.
- If you run any nodes with Task Cap that equals 0 ("UI Only Nodes"), you may notice a trivial reduction of load on these nodes that will be evenly shared amongst all other nodes that have a Task Cap greater than 0.
This aligns some background work more closely with the nodes responsible for task execution and prepares the ground for ongoing improvements to how Octopus handles long-running background operations internally.
We've made internal changes to how background processing work is distributed across nodes in high-availability environments for self-hosted versions of Octopus Server.
Some background processing that previously ran on all node's will now run only on nodes configured to execute tasks where the configured Task Cap is greater than 0.
What this means for you:
This aligns some background work more closely with the nodes responsible for task execution and prepares the ground for ongoing improvements to how Octopus handles long-running background operations internally.