On Thu, 2023-09-14 at 18:28 +0800, Mr.R via Users wrote:
> Hi all，
>
> In Pacemaker-Remote 2.1.6, the pacemaker package is required
> for guest nodes and not for remote nodes. Why is that? What does
> pacemaker do?
> After adding guest node, pacemaker package does not seem to be
> needed.
On Mon, 2023-09-18 at 14:24 +, Knauf Steffen wrote:
> Hi,
>
> we have multiple Cluster (2 node + quorum setup) with more then 100
> Resources ( 10 x VIP + 90 Microservices) per Node.
> If the Resources are stopped/started at the same time the Server is
> under heavy load, which may result
On Monday 18 September 2023 at 16:24:02, Knauf Steffen wrote:
> Hi,
>
> we have multiple Cluster (2 node + quorum setup) with more then 100
> Resources ( 10 x VIP + 90 Microservices) per Node. If the Resources are
> stopped/started at the same time the Server is under heavy load, which may
>
Hi,
we have multiple Cluster (2 node + quorum setup) with more then 100 Resources (
10 x VIP + 90 Microservices) per Node.
If the Resources are stopped/started at the same time the Server is under heavy
load, which may result into timeouts and an unresponsive server.
We configured some Ordering
On Fri, 2023-09-15 at 09:32 +, Adil BOUAZZAOUI wrote:
> Hi Ken,
>
> Any update please?
>
> The idea is clear; I just need to know more information about this 2
> clusters setup:
>
> 1. Arbitrator:
> 1.1. Only one arbitrator is needed for everything: should I use the
> Quorum provided by
Ah, good catch. FYI, we created a hook for situations like this a while
back: resource-agents-deps.target. Which reminds me we really need to
document it ...
To use it, put a drop-in unit under /etc/systemd/system/resource-
agents-deps.target.d/ (any name ending in .conf) with:
[Unit]
