<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:56:31 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-1814] Datastore transactions fail to converge during partitioning</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1814</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;An issue has been reported from the field, which manifested itself as an OpenFlow transaction which does not close and hits OperationLimiter continuously.&lt;/p&gt;</description>
                <environment></environment>
        <key id="29276">CONTROLLER-1814</key>
            <summary>Datastore transactions fail to converge during partitioning</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="1" iconUrl="https://jira.opendaylight.org/images/icons/priorities/blocker.svg">Highest</priority>
                        <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="10000">Done</resolution>
                                        <assignee username="rovarga">Robert Varga</assignee>
                                    <reporter username="rovarga">Robert Varga</reporter>
                        <labels>
                    </labels>
                <created>Mon, 26 Feb 2018 08:41:23 +0000</created>
                <updated>Thu, 12 Apr 2018 18:31:48 +0000</updated>
                            <resolved>Wed, 4 Apr 2018 15:15:53 +0000</resolved>
                                    <version>Boron</version>
                    <version>Carbon</version>
                    <version>Nitrogen</version>
                    <version>Oxygen</version>
                                    <fixVersion>Carbon</fixVersion>
                    <fixVersion>Nitrogen</fixVersion>
                    <fixVersion>Oxygen</fixVersion>
                    <fixVersion>Fluorine</fixVersion>
                                    <component>clustering</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="61207" author="rovarga" created="Mon, 26 Feb 2018 08:44:00 +0000"  >&lt;p&gt;Relevant log snippets on leader:&lt;/p&gt;

&lt;p&gt;2018-01-26 18:21:05,339 | DEBUG | lt-dispatcher-17 | ShardReadWriteTransaction&#160;&#160;&#160;&#160;&#160;&#160;&#160; | 185 - org.opendaylight.controller.sal-clustering-commons - 1.4.3.Boron-SR3 | Got ReceiveTimeout for inactivity - closing transaction member-3-datastore-operational-fe-1-chn-2373-txn-0&lt;br/&gt;
2018-01-26 18:21:05,339 | DEBUG | lt-dispatcher-17 | ShardDataTreeTransactionChain&#160;&#160;&#160; | 191 - org.opendaylight.controller.sal-distributed-datastore - 1.4.3.Boron-SR3 | Aborted transaction ReadWriteShardDataTreeTransaction{id=member-3-datastore-operational-fe-1-chn-2373-txn-0, closed=true&lt;/p&gt;

&lt;p&gt;Log messages on frontend:&lt;/p&gt;

&lt;p&gt;2018-01-26 18:11:41,191 | DEBUG | ntLoopGroup-11-1 | RemoteTransactionContext&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; | 191 - org.opendaylight.controller.sal-distributed-datastore - 1.4.3.Boron-SR3 | Tx member-3-datastore-operational-fe-1-chn-2373-txn-0 sending 1000 batched modifications, ready: false&lt;br/&gt;
2018-01-26 18:11:46,199 | WARN&#160; | ntLoopGroup-11-1 | RemoteTransactionContext&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; | 191 - org.opendaylight.controller.sal-distributed-datastore - 1.4.3.Boron-SR3 | Failed to acquire execute operation permit for transaction member-3-datastore-operational-fe-1-chn-2373-txn-0 on actor ActorSelection&lt;span class=&quot;error&quot;&gt;&amp;#91;Anchor(akka.tcp://opendaylight-cluster-data@10.18.130.52:2550/), Path(/user/shardmanager-operational/member-1-shard-inventory-operational/shard-inventory-member-3:datastore-operational@1:2373-0#-587302156)&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;2018-01-26 18:32:21,289 | WARN&#160; | ntLoopGroup-11-1 | RemoteTransactionContext&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; | 191 - org.opendaylight.controller.sal-distributed-datastore - 1.4.3.Boron-SR3 | Failed to acquire execute operation permit for transaction member-3-d&lt;br/&gt;
atastore-operational-fe-1-chn-2373-txn-0 on actor ActorSelection[Anchor(akka.tcp://opendaylight-cluster-data@10.18.130.52:2550/), Path(/user/shardmanager-operational/member-1-shard-inventory-operational/shard-inventory-member-3:datastore&lt;br/&gt;
-operational@1:2373-0#-587302156)]&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="61208" author="rovarga" created="Mon, 26 Feb 2018 08:49:25 +0000"  >&lt;p&gt;As it turns out OperationLimiter accounting is wrong when faced with a combination of:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Transaction spanning multiple full BatchedModifications&lt;/li&gt;
	&lt;li&gt;AskTimeout of a BatchedModifications request&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;It relies on the BatchedModificationsReply&apos;s content to release permits. Since the request times out, only a single permit is released instead of 1000, leading to the application being throttled and not being able to proceed to submit the transaction.&lt;/p&gt;</comment>
                            <comment id="61209" author="rovarga" created="Mon, 26 Feb 2018 08:50:38 +0000"  >&lt;p&gt;Fluorine: &lt;a href=&quot;https://git.opendaylight.org/gerrit/68757&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/68757&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="29764">CONTROLLER-1825</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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03arj:</customfieldvalue>

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