<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:56:07 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-1661] C: ddb remote listener: write-transactions failes when leader moved</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1661</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;robot:&lt;br/&gt;
&lt;a href=&quot;https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/665/archives/log.html.gz#s1-s54-t1-k2-k12-k1-k1-k1&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/665/archives/log.html.gz#s1-s54-t1-k2-k12-k1-k1-k1&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;logs:&lt;br/&gt;
&lt;a href=&quot;https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/665/archives&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/665/archives&lt;/a&gt;&lt;br/&gt;
2017-05-07 18:21:10,860 | INFO  | h for user karaf | command                          | 266 - org.apache.karaf.log.command - 3.0.8 | ROBOT MESSAGE: Starting test Listener_On_Shard_Leader_Node&lt;/p&gt;

&lt;p&gt;Transaction are produced from all 3 nodes.&lt;br/&gt;
Leader is moved by make-leader-local rpc.&lt;br/&gt;
write-transactions rpc fail on 2 nodes (http status 500), 1 node pass (status 200)&lt;/p&gt;

&lt;p&gt;Failures caused by &lt;br/&gt;
TransactionCommitFailedException&lt;/p&gt;
{message=canCommit encountered an unexpected failure, errorList=[RpcError [message=canCommit encountered an unexpected failure, severity=ERROR, errorType=APPLICATION, tag=operation-failed, applicationTag=null, info=null, cause=akka.pattern.AskTimeoutException: Ask timed out on [ActorSelection[Anchor(akka.tcp://opendaylight-cluster-data@10.29.12.160:2550/), Path(/user/shardmanager-config/member-1-shard-default-config)]] after [30000 ms]. Sender[null] sent message of type \&quot;org.opendaylight.controller.cluster.datastore.messages.BatchedModifications\&quot;.]]}
&lt;p&gt;\n\tat &lt;/p&gt;

&lt;p&gt;which are the same as in &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-1660&quot; title=&quot;C: ddb leader isolation:  after node rejoin within transaction timout write-transactions returned 500 from all nodes&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-1660&quot;&gt;&lt;del&gt;CONTROLLER-1660&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="26215">CONTROLLER-1661</key>
            <summary>C: ddb remote listener: write-transactions failes when leader moved</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="pgubka@cisco.com">Peter Gubka</reporter>
                        <labels>
                    </labels>
                <created>Sun, 7 May 2017 22:53:00 +0000</created>
                <updated>Tue, 25 Jul 2023 08:24:35 +0000</updated>
                            <resolved>Mon, 8 May 2017 13:04:02 +0000</resolved>
                                                                    <component>clustering</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="52119" author="tpantelis" created="Mon, 8 May 2017 13:04:02 +0000"  >&lt;p&gt;This is expected with ask-based protocol. This was the main reason for the new tell-based. I would suggest testing this scenario with tell-based only.&lt;/p&gt;</comment>
                    </comments>
                    <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>8394</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=8394]]></customfieldvalue>

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

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