J2K7GMWRL7:async-replicator $ zgrep -ai "onStub" ar.* | grep "#######-####-####-####-#######"ar.1.log:2025-04-30T20:20:18.945Z INFO NsxRpcStubManager-0 ReplicatorToReplicatorRpcClient 3601709 - [nsx@6876 comp="global-manager" level="INFO" subcomp="async-replicator"] onStubUp:: remoteSite=#######-####-####-####-#######ar.1.log:2025-04-30T20:20:18.945Z INFO NsxRpcStubManager-0 InterSiteProtocolHandlerImpl 3601709 - [nsx@6876 comp="global-manager" level="INFO" subcomp="async-replicator"] onStubUp:: remoteSite=#######-####-####-####-#######ar.1.log:2025-04-30T20:20:18.983Z INFO ForkJoinPool.commonPool-worker-3 ReplicatorToReplicatorRpcClient 3601709 - [nsx@6876 comp="global-manager" level="INFO" subcomp="async-replicator"] onStubDown:: remoteSite=#######-####-####-####-#######ar.1.log:2025-04-30T20:20:18.983Z INFO ForkJoinPool.commonPool-worker-3 InterSiteProtocolHandlerImpl 3601709 - [nsx@6876 comp="global-manager" level="INFO" subcomp="async-replicator"] onStubDown:: remoteSite=#######-####-####-####-#######
J2K7GMWRL7:async-replicator $ grep "checkAndSetLeader: remote s" ar.1.log | grep "#######-####-####-####-#######"2025-04-30T20:20:16.739Z INFO NsxRpcStubManager-0 NsxRpcStubManager 3601709 SYSTEM [nsx@6876 comp="global-manager" level="INFO" subcomp="async-replicator"] checkAndSetLeader: remote site #######-####-####-####-#######, aph #######-####-####-####-#######, isLeader=false2025-04-30T20:20:16.770Z INFO NsxRpcStubManager-0 NsxRpcStubManager 3601709 SYSTEM [nsx@6876 comp="global-manager" level="INFO" subcomp="async-replicator"] checkAndSetLeader: remote site #######-####-####-####-#######, aph #######-####-####-####-#######, isLeader=true2025-04-30T20:20:19.678Z INFO NsxRpcStubManager-1 NsxRpcStubManager 3601709 SYSTEM [nsx@6876 comp="global-manager" level="INFO" subcomp="async-replicator"] checkAndSetLeader: remote site #######-####-####-####-####### aph #######-####-####-####-#######, isLeader=false
VMware NSX-T 4.x
Connection to LM went down and came back up after few seconds. As a result, in GM ReplicatorToReplicator stub to remote site goes down and comes up. Stub down thread went to idle and by the time it completed its task, connection got established Stub-up thread completed. Stub down thread resumed after sleep and marked the connection to be down.
restart async-replicator-service in GM node:
service async-replicator-service restart