Xmem is stuck :- Couchbase on Kubernetes and XDCR spanning AWS ap-south-1 and ap-west-1 regions

Describing the setup:

VPC-1 (ap-south-1) using both the AZs (ap-south-1a & ap-south-1b)
Kubernetes v1.10.3
Couchbase Autonomous Operator v1.0 GA
Couchbase Cluster created: cb-att-in1
Bucket: travel-sample

VPC-2 (us-west-1) using both the AZs (us-west-1a & us-west-1b)
Kubernetes v1.10.3
Couchbase Autonomous Operator v1.0 GA
Couchbase Cluster created: cb-att-us
Bucket: b1-us

Both the VPC are connected using VPC Peering connection (using the same AWS account)

There was XDCR no filtering defined.

Issue:
—
I got below error all through the XDCR replication. Although eventually it completed successfully.

2018-10-15 15:47:20 cb-att-1-0000.cb-att-1.default.svc:
Pipeline 69cbe98baeba70b2d8f4bb49045b995a/travel-sample/b1-us failed to start

2018-10-15 15:47:18 cb-att-1-0001.cb-att-1.default.svc:
xmem_69cbe98baeba70b2d8f4bb49045b995a/travel-sample/b1-us_172.16.86.15:31740_0:
Xmem is stuck

Check the PPT attached for the screenshots.
—

More than the fix I am interested in the background information around this issue.