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-976 controller <p>This is specialization of <a href="https://bugs.opendaylight.org/show_bug.cgi?id=1821" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=1821</a> to context similar to <a href="https://bugs.opendaylight.org/show_bug.cgi?id=2283" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=2283</a></p> <p>Yes, applications should not write to a shard lacking a Leader, but installation of a karaf feature causes that, and Leaderless state is probable just at the time when clustering feature is being installed.</p> <p>Basically, perhaps only a configurable transaction timeout is needed to make sure shard finds its Leader quicker.</p> <p>It is also possible that the more responsible component should be config subsystem, detecting this state and re-trying for a (configurable) time.</p> <p>Current workaround is to always verify clustering feature is fully ready before installing more features.</p> <p>A log attached, showing what happens when instance (of 3 node cluster) starts isolated and features are slowly being installed.</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-976

Clustering: Leaderless default shard during feature installation.

Bug Resolved Done Unassigned Vratko Polak Thu, 30 Oct 2014 17:54:47 +0000 Thu, 19 Oct 2017 22:13:14 +0000 Wed, 12 Nov 2014 11:25:12 +0000 Helium mdsal 0 6 <p>Attachment cluster_20141030.log.xz has been added with description: XZipped complete karaf.log</p> <p>It would not be config subsystem, but the cluster database's Module &#8211; createInstance() is required to return a 'working' instance.</p> <p>Since leader re-election can happen at any moment, I think the broker/transaction chain should block applications while the cluster is being formed.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/12215/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/12215/</a> addresses this issue, i.e. on transaction create, the CDS waits (actually retires) a reasonable amount of time (30 sec) for a shard leader to become elected.</p> <p>That patch was merged on Oct 29th and since this bug was reported Oct 30th, I'm assuming you didn't have that patch.</p> <p>Is this ok to close?</p> <p>&gt; Is this ok to close?</p> <p>Yes, I thing FIXED is the correct status right now (as in not CONFIRMED anymore but not VERIFIED yet).</p> Blocks CONTROLLER-890 Development External issue ID 2284 External issue URL ODL SR Target Milestone Rank 0|i02npz: