On 23.04.2024 19:40, Jochen wrote:
On 23. Apr 2024, at 17:41, Andrei Borzenkov wrote:
On 23.04.2024 10:02, Jochen wrote:
When trying to add a remote node to an opt-in cluster, the cluster does not
start the remote resource. When I change the cluster to opt-out the remote
resource is
> On 23. Apr 2024, at 17:41, Andrei Borzenkov wrote:
>
> On 23.04.2024 10:02, Jochen wrote:
>> When trying to add a remote node to an opt-in cluster, the cluster does not
>> start the remote resource. When I change the cluster to opt-out the remote
>> resource is started.
>
> It's not
On 23.04.2024 10:02, Jochen wrote:
When trying to add a remote node to an opt-in cluster, the cluster does not
start the remote resource. When I change the cluster to opt-out the remote
resource is started.
It's not clear what do you mean. Is "remote resource" the resource used
to
On Tue, Apr 23, 2024 at 10:34 AM Klaus Wenninger
wrote:
>
>
> On Tue, Apr 23, 2024 at 9:53 AM NOLIBOS Christophe <
> christophe.noli...@thalesgroup.com> wrote:
>
>> Classified as: {OPEN}
>>
>>
>>
>> Other strange thing.
>>
>> On RHEL 7, corosync is restarted while the “Restart=on-failure » line
On Tue, Apr 23, 2024 at 9:53 AM NOLIBOS Christophe <
christophe.noli...@thalesgroup.com> wrote:
> Classified as: {OPEN}
>
>
>
> Other strange thing.
>
> On RHEL 7, corosync is restarted while the “Restart=on-failure » line is
> commented.
>
> I think also that something changed in the pacemaker
Classified as: {OPEN}
Other strange thing.
On RHEL 7, corosync is restarted while the “Restart=on-failure » line is
commented.
I think also that something changed in the pacemaker behavior, or somewhere
else.
De : Klaus Wenninger
Envoyé : lundi 22 avril 2024 12:41
À : NOLIBOS
On Tue, Apr 23, 2024 at 12:03 AM Jochen wrote:
>
> When trying to add a remote node to an opt-in cluster, the cluster does not
> start the remote resource. When I change the cluster to opt-out the remote
> resource is started.
>
> I guess I have to add a location constraint to allow the cluster
When trying to add a remote node to an opt-in cluster, the cluster does not
start the remote resource. When I change the cluster to opt-out the remote
resource is started.
I guess I have to add a location constraint to allow the cluster to schedule
the resource. Is that correct?
And if yes,
