Actually , I found the error with the help of the RH support.
I was colocating with the Master SAPHanaController resource and thus the
cluster did what I have told it to do ;)
Now, I just colocated (node-attribute=hana_sid_site) with the first backup ip
(which is colocated with the master) and
Damn... I am too hasty.
It seems that the 2 resources I have already configured are also running on the
master.
The colocation constraint is like:
rsc_bkpip3_SAPHana_SID_HDBinst_num with rsc_SAPHana_SID_HDBinst_num-clone
(score: INFINITY) (node-attribute:hana_sid_site) (rsc-role:Started)
Disregard the previous one... it needs 'pcs constraint colocation add' to work.
Best Regards,Strahil Nikolov
On Wed, Mar 31, 2021 at 8:08, Strahil Nikolov wrote:
I guess that feature was added in a later version (still on RHEL 8.2).
pcs constraint colocation bkp2 with Master
I guess that feature was added in a later version (still on RHEL 8.2).
pcs constraint colocation bkp2 with Master rsc_SAPHana__HDB
score=INFINITY node-attribute=hana__site (or using any other attribute)
brings 'pcs constraint help' output.
It seems that it doesn't like the syntax.
Maybe someone
On Wed, Mar 31, 2021 at 8:34 AM Strahil Nikolov wrote:
>
> Damn... I am too hasty.
>
> It seems that the 2 resources I have already configured are also running on
> the master.
>
> The colocation constraint is like:
>
> rsc_bkpip3_SAPHana_SID_HDBinst_num with rsc_SAPHana_SID_HDBinst_num-clone
>
On 30.03.2021 17:42, Ken Gaillot wrote:
>>
>> Colocation does not work, this will force everything on the same node
>> where master is active and that is not what we want.
>
> Nope, you can colocate by node attribute instead of node.
>
> Colocating by node attribute says "put this resource on a
Hi Reid,
in order the colocation to work , it should (logically) look like
pcs constraint colocation add BKP_IP1 with Master
rsc_SAPHana__HDB-clone INFINITY node-attribute=$(attribute
SITE on Master rsc_SAPHana__HDB-clone)
So far , I have created a bash script to:- detect global maintenance and
On Tue, 2021-03-30 at 08:01 +0300, Andrei Borzenkov wrote:
> On 29.03.2021 20:12, Ken Gaillot wrote:
> > On Sun, 2021-03-28 at 09:20 +0300, Andrei Borzenkov wrote:
> > > On 28.03.2021 07:16, Strahil Nikolov wrote:
> > > > I didn't mean DC as a designated coordinator, but as a physical
> > > >
On Tue, 2021-03-30 at 12:05 +, Strahil Nikolov wrote:
> Hi Reid,
>
> in order the colocation to work , it should (logically) look like
>
> pcs constraint colocation add BKP_IP1 with Master
> rsc_SAPHana__HDB-clone INFINITY node-
> attribute=$(attribute SITE on
> Master
Hi Ken, can you provide a prototype code example.
Currently,I'm making a script that will be used in a systemd service managed by
the cluster.Yet, I would like to avoid non-pacemaker solutions.
Best Regards,Strahil Nikolov
On Mon, Mar 29, 2021 at 20:12, Ken Gaillot wrote: On
Sun,
You can try the following and see if it works, replacing the items in angle
brackets (<>).
# pcs constraint colocation add with Master
INFINITY node-attribute=hana__site
However, `pcs constraint colocation add --help` gives no information about
what options it accepts. It just says
On 29.03.2021 20:12, Ken Gaillot wrote:
> On Sun, 2021-03-28 at 09:20 +0300, Andrei Borzenkov wrote:
>> On 28.03.2021 07:16, Strahil Nikolov wrote:
>>> I didn't mean DC as a designated coordinator, but as a physical
>>> Datecenter location.
>>> Last time I checked, the node attributes for all
On Sun, 2021-03-28 at 09:20 +0300, Andrei Borzenkov wrote:
> On 28.03.2021 07:16, Strahil Nikolov wrote:
> > I didn't mean DC as a designated coordinator, but as a physical
> > Datecenter location.
> > Last time I checked, the node attributes for all nodes seemed the
> > same.I will verify that
I didn't mean DC as a designated coordinator, but as a physical Datecenter
location.
Last time I checked, the node attributes for all nodes seemed the same.I will
verify that tomorrow (Monday).
Best Regards,Strahil Nikolov
On Fri, Feb 19, 2021 at 16:51, Andrei Borzenkov wrote:
On Fri,
On 28.03.2021 07:16, Strahil Nikolov wrote:
> I didn't mean DC as a designated coordinator, but as a physical Datecenter
> location.
> Last time I checked, the node attributes for all nodes seemed the same.I will
> verify that tomorrow (Monday).
>
Yes, I was probably mistaken. It is different
>Do you have a fixed relation between node >pairs and VIPs? I.e. must
>A/D always get VIP1, B/E - VIP2 etc?
I have to verify it again, but generally speaking - yes , VIP1 is always on
nodeA/D (master), VIP2 on nodeB/E (worker1) , etc.
I guess I can set negative constraints (-inf) -> VIP1 on
On Fri, Feb 19, 2021 at 2:44 PM Strahil Nikolov wrote:
>
>
> >Do you have a fixed relation between node >pairs and VIPs? I.e. must
> >A/D always get VIP1, B/E - VIP2 etc?
>
> I have to verify it again, but generally speaking - yes , VIP1 is always on
> nodeA/D (master), VIP2 on nodeB/E (worker1)
DC1:- nodeA- nodeB- nodeC
DC2:- nodeD- nodeE- nodeF
DC3:- majority maker
I will have 3 VIPs:VIP1VIP2VIP3
I will have to setup the cluster to:1. Find where is the master HANA resource2.
Place VIP1 on nodeA/nodeD3. Place VIP2 on nodeB/nodeE4. Place VIP3 on
nodeC/nodeF
End Goal:Master on nodeAVIP1
On Fri, Feb 19, 2021 at 10:41 AM Strahil Nikolov wrote:
>
> DC1:
> - nodeA
> - nodeB
> - nodeC
>
> DC2:
> - nodeD
> - nodeE
> - nodeF
>
> DC3:
> - majority maker
>
> I will have 3 VIPs:
> VIP1
> VIP2
> VIP3
>
> I will have to setup the cluster to:
> 1. Find where is the master HANA resource
> 2.
>>> Strahil Nikolov schrieb am 17.02.2021 um 17:46 in
Nachricht <2134183555.2122291.1613580414...@mail.yahoo.com>:
> Hello All,
> I'm currently in a process of building SAP HANA Scale-out cluster and the
> HANA team has asked that all nodes on the active instance should have one IP
> for backup
20 matches
Mail list logo
