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-1721 controller <p>Seen once so far, in Netconf <del>all</del> 3node job. Karaf.log lines are from <span class="error">&#91;0&#93;</span>.</p> <p>This is very similar to <a href="https://jira.opendaylight.org/browse/AAA-132" title="rest-connector-default-impl occasionally takes too long to finish" class="issue-link" data-issue-key="AAA-132">AAA-132</a> but different config subsystem capability is taking too long this time:<br/> 2017-06-11 12:47:31,609 | WARN | saction-28-30'}} | DeadlockMonitor | 103 - org.opendaylight.controller.config-manager - 0.6.1.Carbon | ModuleIdentifier</p> {factoryName='binding-broker-impl', instanceName='binding-broker-impl'} <p> did not finish after 74969 ms</p> <p>Leading to clustering failure:<br/> 2017-06-11 12:47:35,960 | ERROR | Event Dispatcher | AbstractDataStore | 180 - org.opendaylight.controller.sal-distributed-datastore - 1.5.1.Carbon | Shard leaders failed to settle in 90 seconds, giving up</p> <p><span class="error">&#91;0&#93;</span> <a href="https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-clustering-all-carbon/308/odl1_karaf.log.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-clustering-all-carbon/308/odl1_karaf.log.gz</a></p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1721

binding-broker-impl occasionally takes too long to finish

Bug Resolved Won't Do Unassigned Vratko Polak Tue, 13 Jun 2017 11:30:28 +0000 Tue, 25 Jul 2023 08:24:43 +0000 Fri, 5 Oct 2018 15:44:08 +0000 blueprint 0 4 <p>This is probably caused by blueprint service start ordering.</p> <p>The DeadlockMonitor warn does not lead to the clustering error. In fact it's the other way around. CDS waits up to 90s for all shard to elect leaders which blocks all other dependent blueprint containers from starting, including the binding broker which in turn blocks the CSS "binding-broker-impl" module from completing startup, hence the DeadlockMonitor warning. As we've seen in other cases, it seems test environment load can delay startup and node connectivity.</p> Development External issue ID 8678 External issue URL Issue Type Rank 0|i02sbj: