|
We have a CSIT which expects DataStoreUnavailableException to happen after 60 seconds after isolating the client (tell-based protocol).
In the recent run with module-based shards, it happened [0] roughly 50 seconds after isolation.
Karaf.log [1] does not show anything surprising, except from the following not occuring slightly later:
2017-05-14 06:32:57,432 | ERROR | ult-dispatcher-6 | ClientActorBehavior | 197 - org.opendaylight.controller.cds-access-client - 1.1.0.Carbon | member-2-frontend-datastore-config: failed to resolve shard 0
org.opendaylight.controller.cluster.datastore.exceptions.NoShardLeaderException: Shard member-2-shard-default-config currently has no leader. Try again later.
Is this something related to CONTROLLER-1677 or was there a change in shard resolution timeouts? Note that [2] is not merged yet.
[0] https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/684/archives/log.html.gz#s1-s37-t1-k2-k16-k1-k1-k1-k1-k1-k1-k2-k1-k1-k1
[1] https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/684/archives/odl2_karaf.log.gz
[2] https://git.opendaylight.org/gerrit/56874
|