<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:55:41 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[CONTROLLER-1491] Entity Ownership Service: support graceful state handoff</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1491</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;Current entity ownership model does not support stateful failovers, as is the case in changing ownership of a OF connection.&lt;/p&gt;

&lt;p&gt;Essentially there are multiple resources attached to a particular entity: the TCP session which dominates the ability to be a candidate and a datastore transaction chain which is attached to the master role.&lt;/p&gt;

&lt;p&gt;When a master is becoming the slave as part of election, it needs to clean up data store state before the new master can resume operations. This effectively means that if there is a master and the election results indicate that the role needs to be moved to another candidate, we need a &apos;stopping&apos; transition, which is asynchronous and completed by the outgoing master. Once the old master has stopped the new master can be elected.&lt;/p&gt;

&lt;p&gt;In the OF case, this would mean that outgoing leader would initiate TransactionChain.close() and finish &apos;stopping&apos; when the transaction chain callback indicates the shutdown procedure has completed.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="26045">CONTROLLER-1491</key>
            <summary>Entity Ownership Service: support graceful state handoff</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10001">Won&apos;t Do</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="rovarga">Robert Varga</reporter>
                        <labels>
                    </labels>
                <created>Wed, 24 Feb 2016 16:09:21 +0000</created>
                <updated>Tue, 25 Jul 2023 08:24:07 +0000</updated>
                            <resolved>Thu, 24 Aug 2017 13:14:39 +0000</resolved>
                                                                    <component>clustering</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="51339" author="rovarga" created="Wed, 24 Feb 2016 16:12:10 +0000"  >&lt;p&gt;Further analysis is required, as it seems that as long as access to EOS and DS share fate (e.g. they fail reliably at the same time), we can get away with just ensuring EOS prefers master stability and never takes away ownership from a candidate which is still alive.&lt;/p&gt;

&lt;p&gt;If that is the case, it would be sufficient to expose APIs to define entity types such that each entity type has a well-known and application-controlled selection strategy.&lt;/p&gt;</comment>
                            <comment id="51340" author="rovarga" created="Thu, 24 Aug 2017 13:14:39 +0000"  >&lt;p&gt;Cluster Singleton Service has a solution for this problem.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="26980">MDSAL-158</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5420</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=5420]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10308"><![CDATA[New Feature]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10202" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Priority</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10304"><![CDATA[Low]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i02qwf:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>