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-1676 controller <p>This is affecting CSIT results at the node which ends up being a follower in the majority partition, so this might be related to <a href="https://jira.opendaylight.org/browse/AAA-130" title="AAA problems during partitioning and healing cluster" class="issue-link" data-issue-key="AAA-130"><del>AAA-130</del></a>.</p> <p>This prevents testing a scenario when isolation is short enough so that client does not time out.</p> <p>In the recent test, it took 44 seconds to confirm both members agree on the new leader, and ODL took <span class="error">&#91;0&#93;</span> almost 5 second to respond to the final request.</p> <p>Karaf.log <span class="error">&#91;1&#93;</span> shows several suspicious lines between 06:23:51,346 and 06:24:49,542, but it is not clear to me what causes the process to take this long.</p> <p><span class="error">&#91;0&#93;</span> <a href="https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/684/archives/log.html.gz#s1-s33-t1-k2-k11-k2-k1-k1-k6-k2-k1-k5-k1-k3-k1" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/684/archives/log.html.gz#s1-s33-t1-k2-k11-k2-k1-k1-k6-k2-k1-k5-k1-k3-k1</a><br/> <span class="error">&#91;1&#93;</span> <a href="https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/684/archives/odl3_karaf.log.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/684/archives/odl3_karaf.log.gz</a></p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1676

After leader is isolated, new leader is elected too slowly

Bug Resolved Done Tomas Cere Vratko Polak Mon, 15 May 2017 11:20:38 +0000 Tue, 25 Jul 2023 08:24:37 +0000 Tue, 16 May 2017 16:28:09 +0000 clustering 0 2 <p>This also affects <span class="error">&#91;2&#93;</span> prefix-based shards.</p> <p><span class="error">&#91;2&#93;</span> <a href="https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/684/archives/log.html.gz#s1-s35-t2-k2-k11-k1-k1-k1-k6-k2-k1-k2-k1-k1-k3-k3-k1" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/684/archives/log.html.gz#s1-s35-t2-k2-k11-k1-k1-k1-k6-k2-k1-k2-k1-k1-k3-k3-k1</a></p> <p>Upon investigation it seems the leader was elected in ~5 seconds, however jolokia on member-3 seemed to take around 45 seconds of retries to produce a response in the 5 seconds thats expected in the robot suites. Will add rpc's into cluster-admin for getting the shard role to get around jolokia.</p> <p>These introduce the get-shard-role rpcs into cluster admin, which should bypass the slowness of jolokia:</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/57131/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/57131/</a><br/> <a href="https://git.opendaylight.org/gerrit/#/c/57133/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/57133/</a></p> Development External issue ID 8447 External issue URL Issue Type Rank 0|i02s1j: