[pve-devel] [PATCH docs 3/5] ha: rules: document crs behavior for split positive resource affinity
Daniel Kral
d.kral at proxmox.com
Tue Aug 5 09:50:30 CEST 2025
Hey Michael!
Thanks for taking a look!
On Tue Aug 5, 2025 at 9:42 AM CEST, Michael Köppl wrote:
> On 8/4/25 16:12, Daniel Kral wrote:
>> Signed-off-by: Daniel Kral <d.kral at proxmox.com>
>> ---
>> ha-manager.adoc | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/ha-manager.adoc b/ha-manager.adoc
>> index 5d75287..e18a14d 100644
>> --- a/ha-manager.adoc
>> +++ b/ha-manager.adoc
>> @@ -787,6 +787,11 @@ HA resources `vm:101` and `vm:102` are each in a positive resource affinity
>> rule, then it is the same as if `vm:100`, `vm:101` and `vm:102` would have been
>> in a single positive resource affinity rule.
>>
>> +NOTE: If the HA resources of a positive resource affinity rule are currently
>> +running on different nodes, the CRS will move the HA resources to the node,
>> +where most of them are running already. If there is a tie in the HA resource
>> +count, the node with the alphabetically first name is chosen.
>
> maybe something like:
>
> "the node whose name appears first alphabetically is selected"
ACK, I'll use "first in alphabetical order" though as it seems ambiguous
to me whether first comes before or after alphabetically
>
> just a suggestion, though
>
>> +
>> However, suppose there are computationally expensive, and/or distributed
>> programs running on the HA resources `vm:200` and `ct:300`, for example,
>> sharded database instances. In that case, running them on the same node could
More information about the pve-devel
mailing list