Problem found !  In the second cluster, you need to create the Storage Pool, but DO NOT create a VDC.  Even though there isnt an explicit VDC entity, you can still retrieve the VDC key on the second cluster.  Then return to the primary cluster and create the VDC using the key and IP addresses as appropriate.  I am now seeing the replication group active, and data being consumed on the second cluster when data is only uploaded to the primary cluster - so working as per design.
Hi All,  I have deployed a multi-node instance of ECS community edition with 3.0 code base.  There are 4 nodes, each with 4 x 120GB eager zero think provisioned LUNs, sitting on a SAN capable of almost 1000Mbyte/sec controller level throughput (from IOPS generation test utilities)  Deployment went smoothly, and I have created the storage pool across all 4 nodes. However, the storage pool as still not finished initializing after 11 days.  When i check the node statistics, i see a 1Mbit/sec network activity and 5% CPU on all nodes doing whatever background tasks are needed. The DT initialization stats got to 384 DT very quickly, then grew to 480 after about 6 days, and has been there ever since. I believe it needs to get to 1960?  Is there any way to connect inside the docker containers to change the priority of DTInit process? There is no lack of CPU, network or storage resources in my vSphere cluster to support this.  I am waiting on this to complete (ie change to Ready status) so that i can create geo-replicated VDCs between this multi-node cluster, and a second one sitting in another network segment.   Any help would be appreciated!
ECS 3.0 Multinode Initialization slow?