On Feb 13, 2019, at 2:22 AM, Robert Varga <nite@...> wrote:

On 12/02/2019 19:44, Luis Gomez wrote:

Hi everybody,

FYI I have just tried OFP cluster test with "tell-based" protocol:

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/openflowplugin-csit-3node-clustering-only-neon/180/robot-plugin/log.html.gz

My observations:

1) node/port down events do not clear links in topology, this is why all topology check test fail.

I think this is related to the transactions not commit in 5 seconds,
hence masters are not created.

2) some WARNs are flooding the log:

2019-02-12T00:26:30,055 | WARN | opendaylight-cluster-data-shard-dispatcher-33 | FrontendClientMetadataBuilder | 223 - org.opendaylight.controller.sal-distributed-datastore - 1.9.0.SNAPSHOT | member-1-shard-inventory-operational: Unknown history for aborted transaction member-1-datastore-operational-fe-0-txn-30-2, ignoring

2019-02-12T00:26:30,056 | WARN | opendaylight-cluster-data-shard-dispatcher-33 | FrontendClientMetadataBuilder | 223 - org.opendaylight.controller.sal-distributed-datastore - 1.9.0.SNAPSHOT | member-1-shard-inventory-operational: Unknown history for aborted transaction member-2-datastore-operational-fe-0-txn-19-1, ignoring

2019-02-12T00:26:30,056 | WARN | opendaylight-cluster-data-shard-dispatcher-33 | FrontendClientMetadataBuilder | 223 - org.opendaylight.controller.sal-distributed-datastore - 1.9.0.SNAPSHOT | member-1-shard-inventory-operational: Unknown history for aborted transaction member-3-datastore-operational-fe-0-txn-7-1, ignoring

This is interesting, as it starts happening for the same transaction on
all shard members and these are standalone transactions, for which the
history should always be there.

Can you re-run the test with debug on
org.opendaylight.controller.cluster.datastore.FrontendClientMetadataBuilder,
please?

3) The cluster perf test does not pass: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/openflowplugin-csit-3node-clustering-perf-bulkomatic-only-neon/180/robot-plugin/log.html.gz

I do not know if we still pursue to switch the cluster protocols, at least after this test it does not seem an straight forward change.

I'd like to be able to ditch the old one, but it seems we need to shake
some bugs out :(

Thanks,
Robert