https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-1660 controller <p>robot:<br/> <a href="https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/665/archives/log.html.gz#s1-s50-t1-k2-k18-k1-k1" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/665/archives/log.html.gz#s1-s50-t1-k2-k18-k1-k1</a></p> <p>scenarion:<br/> transactions are produced on each node<br/> the leader is isolated<br/> within few seconds new leader is eleceted (less than 10s)<br/> isolated node is rejoined then and tests waits for shards to be sync on all nodes<br/> write-trancasions rpc should return 200s, but 500s are returned from all nodes</p> <p>logs <a href="https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/665/archives/" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/665/archives/</a><br/> 2017-05-07 18:11:17,081 | INFO | h for user karaf | command | 266 - org.apache.karaf.log.command - 3.0.8 | ROBOT MESSAGE: Starting test Healing_Within_Transaction_Timeout</p> <p>bug may be related to 8372</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1660

C: ddb leader isolation: after node rejoin within transaction timout write-transactions returned 500 from all nodes

Bug Resolved Won't Do Unassigned Peter Gubka Sun, 7 May 2017 22:18:56 +0000 Tue, 25 Jul 2023 08:24:34 +0000 Mon, 8 May 2017 13:58:30 +0000 clustering 0 1 <p>All 3 nodes returned TransactionCommitFailedException cause by akka timeout, but the first stacktrace comes from<br/> org.opendaylight.controller.cluster.datastore.messages.ReadyLocalTransaction<br/> other 2 come from <br/> org.opendaylight.controller.cluster.datastore.messages.BatchedModifications</p> <p>This is expected with ask-based protocol. This was the main reason for the new tell-based. I would suggest testing this scenario with tell-based only.</p> <p>(In reply to Tom Pantelis from comment #2)<br/> &gt; This is expected with ask-based protocol. This was the main reason for the<br/> &gt; new tell-based. I would suggest testing this scenario with tell-based only.</p> <p>It was tested with tell-based=true. Before every testing suite there was an odl restart with certain tell-based setting (true or false). In this case it was a restart with tell-based=true.</p> <p>You're saying that it failed with AskTimeout for BatchedModifications and ReadyLocalTransaction. That is the ask-based protocol.</p> Development External issue ID 8393 External issue URL Rank 0|i02rxz: