Hi,
we are testing the etcd discovery, instead of jgroups...
There is one etcd instance on machine, and multiple fabric3 nodes - so only localhost communication.
It doesn't look like the nodes in single domain, in different zones, knows about each other:
I can see logs on nodeExecutors1 in libradeExecutors:node:zoneExecutors1:
[INFO 02.11.2015 17:28:04.903] Fabric3 ready [Name: libradeExecutors:node:zoneExecutors1:nodeExecutors1, Domain: libradeExecutors, Zone: zoneExecutors1, Mode:NODE, Environment: executors]
and I can see logs on nodeExecutors2 in libradeExecutors:node:zoneExecutors2:
[INFO 02.11.2015 17:28:10.587] Fabric3 ready [Name: libradeExecutors:node:zoneExecutors2:nodeExecutors2, Domain: libradeExecutors, Zone: zoneExecutors2, Mode:NODE, Environment: executors]
but there is no log, that would describe that they know about each other, like it was in the past...
Presence of logs in not the problem though.
When I deploy composites, which were working on jgroups discovery based domain, they are not working now:
org.fabric3.api.host.domain.AssemblyException: Target component for reference fabric3://libradeExecutors/BSIMSimulationBrokerConnectorCreatorComponent#ICoreTradeBookServiceRemote not found: fabric3://libradeExecutors/CoreTradeBookComponent (librade-bc-simulation-bsim-1.3.0-SNAPSHOT.jar)
Target component for reference fabric3://libradeExecutors/ComlaJavaExecutor#ICoreTradeBookServiceRemote not found: fabric3://libradeExecutors/CoreTradeBookComponent (librade-comla-executor-java-1.3.0-SNAPSHOT.jar)
Target component for reference fabric3://libradeExecutors/ComlaJavaExecutor#ICoreIOServiceRemote not found: fabric3://libradeExecutors/CoreIOComponent (librade-comla-executor-java-1.3.0-SNAPSHOT.jar)
Target component for reference fabric3://libradeExecutors/ComlaJavaExecutor#IBrokerConnectorRouterTrading not found: fabric3://libradeExecutors/BrokerConnectorRouterTradingComponent (librade-comla-executor-java-1.3.0-SNAPSHOT.jar)
Target component for reference fabric3://libradeExecutors/ComlaRExecutor#ICoreTradeBookServiceRemote not found: fabric3://libradeExecutors/CoreTradeBookComponent (librade-comla-executor-R-1.3.0-SNAPSHOT.jar)
Target component for reference fabric3://libradeExecutors/ComlaRExecutor#ICoreIOServiceRemote not found: fabric3://libradeExecutors/CoreIOComponent (librade-comla-executor-R-1.3.0-SNAPSHOT.jar)
Target component for reference fabric3://libradeExecutors/ComlaRExecutor#IBrokerConnectorRouterTrading not found: fabric3://libradeExecutors/BrokerConnectorRouterTradingComponent (librade-comla-executor-R-1.3.0-SNAPSHOT.jar)
Target component for reference fabric3://libradeExecutors/LMAXSimulationBrokerConnectorCreatorComponent#ICoreTradeBookServiceRemote not found: fabric3://libradeExecutors/CoreTradeBookComponent (librade-bc-simulation-lmax-1.3.0-SNAPSHOT.jar)
Target component for reference fabric3://libradeExecutors/NotificationsComponent#ICoreAlgorithmServiceRemote not found: fabric3://libradeExecutors/CoreAlgorithmComponent (librade-mdm-notifications-1.3.0-SNAPSHOT.jar)
at org.fabric3.fabric.domain.AbstractDomain.instantiateAndDeploy(AbstractDomain.java:160)
at org.fabric3.fabric.domain.AbstractDomain.include(AbstractDomain.java:136)
at org.fabric3.fabric.domain.AbstractDomain.include(AbstractDomain.java:95)
at org.fabric3.contribution.scanner.impl.ContributionDirectoryScanner.onEvent(ContributionDirectoryScanner.java:144)
at org.fabric3.fabric.runtime.event.EventServiceImpl.publish(EventServiceImpl.java:49)
at org.fabric3.fabric.runtime.DefaultCoordinator.startRuntime(DefaultCoordinator.java:101)
at org.fabric3.fabric.runtime.DefaultCoordinator.start(DefaultCoordinator.java:67)
at org.fabric3.runtime.standalone.server.Fabric3Server.start(Fabric3Server.java:181)
at org.fabric3.runtime.standalone.server.Fabric3Server.main(Fabric3Server.java:85)
how to set up domain with etcd so that the nodes knows about each other?
Tomas