KB Article #179875

node already registered when Active\Active cluster and registering it in CG

Problem

CFT Active\Active cluster and registering it in CG


Error in CG registration for 2nd node "node already registered"


COPUI.TRC:

ERR SYS PID=56536 navigatorNotifRecv: Central Governance: recv self-registration response error: (409) Already registered: conflict on instanceId:instanceGroup or on host:port : Registration rejected. Reason: node with this inst

MSG ALL PID=56536 Central Governance: successfully registered (registration ID is 1179978262)

MSG ALL PID=56536 Copilot is shutting down


Resolution


Issue is related file locking.


A file lock from one host cannot be seen from the second host and vice-versa.


In a A/A only one Copilot is responsible to register to CG the entire Transfer CFT instance.


To do that, Copilot uses a file lock. Since the file lock is not propagated between NFS clients, both Copilots try to register at the same time.

This is the reason why of the error "Already registered".



Solution:

Solve the file lock issue between the two NFS clients and server.

This will require the shared file system and sys admin team to fix it.