If the Relay node in a Composite cluster should ever point to the incorrect Primary node, you can perform the following procedure to re-point the replicator to the desired Primary node.
For example, say we have a composite cluster global,
with nodes db1, db2 and db3 in alpha and db4, db5 and
db6 in beta. db1 is the Primary and db4 is the relay.
In the output below, the relay node db4 shows that its replicator is using db2 as the Primary instead of db1:
+---------------------------------------------------------------------------------+ |db4(relay:ONLINE, progress=5, latency=0.352) | |STATUS [OK] [2025/01/28 02:39:49 PM UTC] | +---------------------------------------------------------------------------------+ | MANAGER(state=ONLINE) | | REPLICATOR(role=relay, master=db2, state=ONLINE) | | DATASERVER(state=ONLINE) | | CONNECTIONS(created=8108, active=0) | +---------------------------------------------------------------------------------+
Use the cctrl replicator command to adjust the relay source:
shell>cctrlTungsten Cluster 7.0.3 build 141 west: session established [LOGICAL] /beta >set policy maintenance[LOGICAL] /beta >replicator db4 offline[LOGICAL] /beta >replicator db4 relay alpha/db1[LOGICAL] /beta >set policy automatic[LOGICAL] /beta >ls+---------------------------------------------------------------------------------+ |db4(relay:ONLINE, progress=5, latency=0.352) | |STATUS [OK] [2025/01/28 02:39:49 PM UTC] | +---------------------------------------------------------------------------------+ | MANAGER(state=ONLINE) | | REPLICATOR(role=relay, master=db1, state=ONLINE) | | DATASERVER(state=ONLINE) | | CONNECTIONS(created=0, active=0) | +---------------------------------------------------------------------------------+