Hi
When does the following happen where one instance (172.17.6.26) quarantines
another instance (172.17.6.27) and causes it to restart? Of my 3 controller
instances (172.17.6.26, 172.17.6.27 and 172.17.6.28), 172.17.6.28 was the
one isolated, but a different instance got quarantines. My akka.conf does
not have auto-down-unreachable-after set.


2017-04-04 03:22:28,997 | WARN  | lt-dispatcher-38 |
QuarantinedMonitorActor          | 187 -
org.opendaylight.controller.sal-clustering-commons - 1.4.2.Boron-SR2 | Got
quarantined by akka.tcp://opendaylight-cluster-data@172.17.6.26:2550
2017-04-04 03:22:28,997 | WARN  | lt-dispatcher-38 |
ActorSystemProviderImpl          | 193 -
org.opendaylight.controller.sal-distributed-datastore - 1.4.2.Boron-SR2 |
Restarting karaf container
2017-04-04 03:22:29,000 | WARN  | ult-dispatcher-4 | Remoting
          | 176 - com.typesafe.akka.slf4j - 2.4.7 | Tried to associate with
unreachable remote address [akka.tcp://
opendaylight-cluster-data@172.17.6.26:2550]. Address is now gated for 5000
ms, a
ll messages to this address will be delivered to dead letters. Reason: [The
remote system has quarantined this system. No further associations to the
remote system are possible until this system is restarted.]
2017-04-04 03:22:29,008 | INFO  |  Bundle Shutdown | ConfigRegistryImpl
          | 125 - org.opendaylight.controller.config-manager -
0.5.2.Boron-SR2 | ConfigRegistry closing - destroying 53 modules


Thanks
Srini.
_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

Reply via email to