Klaus,
yes, these constraints were defined by pcs after manual move (pcs resource
move) and help about this action is clear:
Usage: pcs resource move...
move [destination node] [--master] [lifetime=]
[--wait[=n]]
Move the resource off the node it is currently running on by
On Tue, May 28, 2024 at 12:34 PM Александр Руденко
wrote:
> Andrei, thank you!
>
> I tried to find node's scores and have found location constraints for
> these 3 resources:
>
> pcs constraint
> Location Constraints:
> Resource: fsmt-28085F00
> Enabled on:
> Node: vdc16
On Tue, May 28, 2024 at 10:40 AM Александр Руденко
wrote:
> Hi!
>
> I can't understand this strange behavior, help me please.
>
> I have 3 nodes in my cluster, 4 vCPU/8GB RAM each. And about 70 groups, 2
> resources in each group. First one resource is our custom resource which
> configures
Andrei, thank you!
I tried to find node's scores and have found location constraints for these
3 resources:
pcs constraint
Location Constraints:
Resource: fsmt-28085F00
Enabled on:
Node: vdc16 (score:INFINITY) (role:Started)
Resource: fsmt-41CC55C0
Enabled on:
Node: vdc16
On Tue, May 28, 2024 at 11:39 AM Александр Руденко wrote:
>
> Hi!
>
> I can't understand this strange behavior, help me please.
>
> I have 3 nodes in my cluster, 4 vCPU/8GB RAM each. And about 70 groups, 2
> resources in each group. First one resource is our custom resource which
> configures
Hi!
I can't understand this strange behavior, help me please.
I have 3 nodes in my cluster, 4 vCPU/8GB RAM each. And about 70 groups, 2
resources in each group. First one resource is our custom resource which
configures Linux VRF and second one is systemd unit. Everything works fine.
We have
