Adding a data center : 4.19.01 with 4.19.06

abiram8
Participant IV

Hi,

As per link indicating

I have two Parallel set up 4.19.01 (current state) in RHEL 6.9 & new set up 4.19.06 (Future state) in RHEL 7.7 to replace 4.19.01 (Future one 4.19.06 is the new D.C set up installed newly)

In order to switch over from 4.19.01 to 4.19.06 I am following indicated steps in same link.to achieve the Zero down time experience for Users.

The step indicates about adding additional D.C & if we follow listed D.C expansion per listed steps

Step 1: (ZK of 4.19.01 (dc-1) to expand with ZK of 4.19.06 (dc-2)

Step 2: Open LDAP of 4.19.01 (dc-1) to expand with OpenLDAP of 4.19.06 (dc-2).

Step :3 have clustered Postgres in each DC

Two Postgres in 4.19.01 and Two Postgres in 4.19.06. : Initially one of the Postgres in 4.19.01 is Master and others joins as Slave, then Make the one of Postgres in 4.19.06 as Master and 3 remaining Postgres as slave

Step 4: ZK : Expand the 4.19.01 with 4.19.06 ZK.

Once this is done tested the required/critical API and route the L.B from 4.19.01 Router to 4.19.06 Router, then decommission the 4.19.01 (Offcouse will back up 4.19.01 and 4.19.06 on regular basis)

Do we have any challenges, if we are expanding per link with different versions of Apigee components and decommission older set up.

We did not want to migrate the same O.S and Apigee to current,but had to move from 4.9.01 to 4.19.06 in the listed way. Do we have any issues ? when expanding ZK, OpenLDAP, CS and Postgres in listed way

Docs in other place indicates about having same version of Apigee but if i have two D.C once D.C of 4.19.01 and another D.C of 4.19.06 to achieve Zero Downtime experience for consumer, shpuld work fine..

Let me know your comments/suggestions with respect to indicated design and set up to avoid any surprises.

0 1 162
1 REPLY 1

Not applicable

Apigee suggests all its components should be in the same version. It doesn't work with different versions of components. For multi-dc also the same applies.