On Wed, Jun 28, 2023 at 7:38 AM Klaus Wenninger wrote:
>
>
> On Wed, Jun 28, 2023 at 3:30 AM Priyanka Balotra <
> priyanka.14balo...@gmail.com> wrote:
>
>> I am using SLES 15 SP4. Is the no-quorum-policy still supported?
>>
>>
> Thanks
>> Priyanka
>>
>> On Wed, 28 Jun 2023 at 12:46 AM, Ken
On Wed, Jun 28, 2023 at 3:30 AM Priyanka Balotra <
priyanka.14balo...@gmail.com> wrote:
> I am using SLES 15 SP4. Is the no-quorum-policy still supported?
>
> Thanks
> Priyanka
>
> On Wed, 28 Jun 2023 at 12:46 AM, Ken Gaillot wrote:
>
>> On Tue, 2023-06-27 at 22:38 +0530, Priyanka Balotra wrote:
I am using SLES 15 SP4. Is the no-quorum-policy still supported?
Thanks
Priyanka
On Wed, 28 Jun 2023 at 12:46 AM, Ken Gaillot wrote:
> On Tue, 2023-06-27 at 22:38 +0530, Priyanka Balotra wrote:
> > In this case stonith has been configured as a resource,
> > primitive stonith-sbd
On Tue, 2023-06-27 at 22:38 +0530, Priyanka Balotra wrote:
> In this case stonith has been configured as a resource,
> primitive stonith-sbd stonith:external/sbd
>
> For it to be functional properly , the resource needs to be up, which
> is only possible if the system is quorate.
Pacemaker can
In this case stonith has been configured as a resource,
*primitive stonith-sbd stonith:external/sbd*
For it to be functional properly , the resource needs to be up, which is
only possible if the system is quorate.
Hence our requirement is to make the system quorate even if one Node of the
cluster
On Tue, Jun 27, 2023 at 5:24 PM Andrei Borzenkov
wrote:
> On 27.06.2023 07:21, Priyanka Balotra wrote:
> > Hi Andrei,
> > After this state the system went through some more fencings and we saw
> the
> > following state:
> >
> > :~ # crm status
> > Cluster Summary:
> >* Stack: corosync
> >
On 27.06.2023 07:21, Priyanka Balotra wrote:
Hi Andrei,
After this state the system went through some more fencings and we saw the
following state:
:~ # crm status
Cluster Summary:
* Stack: corosync
* Current DC: FILE-2 (version
On Tue, 2023-06-27 at 09:51 +0530, Priyanka Balotra wrote:
> Hi Andrei,
> After this state the system went through some more fencings and we
> saw the following state:
>
> :~ # crm status
> Cluster Summary:
> * Stack: corosync
> * Current DC: FILE-2 (version
Hi Andrei,
After this state the system went through some more fencings and we saw the
following state:
:~ # crm status
Cluster Summary:
* Stack: corosync
* Current DC: FILE-2 (version
2.1.2+20211124.ada5c3b36-150400.2.43-2.1.2+20211124.ada5c3b36) - partition
with quorum
* Last updated: Mon
On 26.06.2023 21:14, Priyanka Balotra wrote:
Hi All,
We are seeing an issue where we replaced no-quorum-policy=ignore with other
options in corosync.conf order to simulate the same behaviour :
* wait_for_all: 0*
*last_man_standing: 1last_man_standing_window: 2*
There
Hi All,
We are seeing an issue where we replaced no-quorum-policy=ignore with other
options in corosync.conf order to simulate the same behaviour :
* wait_for_all: 0*
*last_man_standing: 1last_man_standing_window: 2*
There was another property (auto-tie-breaker) tried
11 matches
Mail list logo
