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-1740 controller <p>This is continuation of <a href="https://jira.opendaylight.org/browse/CONTROLLER-1731" title="it provider: produce-transactions does not close itemProducer on success" class="issue-link" data-issue-key="CONTROLLER-1731"><del>CONTROLLER-1731</del></a> (from comment 3 on) with better title and less old information.</p> <p>The test scenario: Each member starts transaction producer. Leader is isolated for a time slightly longer than 120 seconds. New leader is elected, tests sees the isolated produred report RequestTimeoutException, at that point the preoducer unregisters, while the member is still isolated.<br/> After rejoin, the test attempts to start new producer. During producer registration, frontend rejects it, as the new leader still believes the old producer is registered.</p> <p>The complete karaf.log is here <span class="error">&#91;10&#93;</span>, the final relevant segment:<br/> 2017-07-11 11:58:31,266 | DEBUG | qtp138207402-77 | ShardedDOMDataTree | 147 - org.opendaylight.mdsal.dom-broker - 2.2.1.SNAPSHOT | Creating producer org.opendaylight.mdsal.dom.broker.ShardedDOMDataTreeProducer@e86db<br/> 2017-07-11 11:58:31,266 | TRACE | qtp138207402-77 | ShardedDOMDataTree | 147 - org.opendaylight.mdsal.dom-broker - 2.2.1.SNAPSHOT | Adding subtree DOMDataTreeIdentifier{datastore=CONFIGURATION, root=/(tag:opendaylight.org<br/> ,2017:controller:yang:lowlevel:target?revision=2017-02-15)id-ints/id-int/id-int[</p> {(tag:opendaylight.org,2017:controller:yang:lowlevel:target?revision=2017-02-15)id=prefix-3} <p>]} to map.<br/> 2017-07-11 11:58:31,291 | ERROR | qtp138207402-77 | ContainerResponse | 68 - com.sun.jersey.jersey-server - 1.17.0 | The RuntimeException could not be mapped to a response, re-throwing to the HTTP container<br/> org.opendaylight.controller.cluster.datastore.exceptions.TimeoutException: Sending message class org.opendaylight.controller.cluster.sharding.messages.ProducerCreated to actor Actor<a href="#725503709" target="_blank" rel="noopener">akka://opendaylight-cluster-data/user/ShardedDOMDataTreeFrontend#725503709</a> failed. Try again later.<br/> at org.opendaylight.controller.cluster.datastore.utils.ActorContext.executeOperation(ActorContext.java:318)<br/> at org.opendaylight.controller.cluster.sharding.DistributedShardedDOMDataTree.createProducer(DistributedShardedDOMDataTree.java:305)<br/> at Proxy547e830a_606c_4629_8e3c_527344f37367.createProducer(Unknown Source)<br/> at Proxya432b2a8_a907_437a_a7a2_58deacd6d56e.createProducer(Unknown Source)<br/> at org.opendaylight.controller.clustering.it.provider.impl.ProduceTransactionsHandler.start(ProduceTransactionsHandler.java:67)<br/> ...</p> <p><span class="error">&#91;10&#93;</span> <a href="https://logs.opendaylight.org/sandbox/jenkins091/controller-csit-3node-clustering-li-only-carbon/4/odl3_karaf.log.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/sandbox/jenkins091/controller-csit-3node-clustering-li-only-carbon/4/odl3_karaf.log.gz</a></p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1740

Producer un-registration on isolated node is never propagated to the rest of the cluster

Bug Resolved Won't Do Unassigned Vratko Polak Wed, 12 Jul 2017 12:18:38 +0000 Tue, 25 Jul 2023 08:24:45 +0000 Tue, 13 Jul 2021 11:27:41 +0000 clustering 0 3 <p>This boils down to producer registrations being disseminated via ShardDataTreeActor messages, which do not work during isolation.</p> <p>I think the proper fix is to make cluster-wide producers replicated via a runtime shard analogue to sharding table shard.</p> <p>If producer registration is to be reworked, I think we also need automatic unregistration on timeout, to prevent unreachable nodes from owning subtrees indefinitely.</p> <p>Also, when new producer is being registered, every possible subtree overlap should be detected. That means the free-standing producer should see no ancestor producer, but also no descendant producer.</p> <p>This includes inter-member race conditions, for example member-1 trying to register for /a while member-2 tries to register for /a/b.</p> <p>The entire implementation was removed in <font color="#000000"><a href="https://jira.opendaylight.org/browse/CONTROLLER-1977" title="Remove Producer/Consumer/ShardedDataTree implementation" class="issue-link" data-issue-key="CONTROLLER-1977"><del>CONTROLLER-1977</del></a></font></p> Relates MDSAL-397 Development External issue ID 8845 External issue URL Issue Type ODL SR Target Milestone Rank 0|i02sfr: