<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:56:06 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-1654] C: write-transactions rpc does not return</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1654</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;(my job #597)&lt;br/&gt;
used odl: &lt;a href=&quot;https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/integration/distribution/distribution-karaf/0.6.0-SNAPSHOT/distribution-karaf-0.6.0-20170503.152424-68.zip&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/integration/distribution/distribution-karaf/0.6.0-SNAPSHOT/distribution-karaf-0.6.0-20170503.152424-68.zip&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;is built from controller=33/56433/5&lt;br/&gt;
&lt;a href=&quot;https://jenkins.opendaylight.org/releng/view/integration/job/integration-multipatch-test-carbon/11/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/view/integration/job/integration-multipatch-test-carbon/11/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;write-transactions is called on the first node of 3 node cluster with params&lt;br/&gt;
url: &lt;a href=&quot;http://172.17.0.4:8181/restconf/operations/odl-mdsal-lowlevel-control:write-transactions&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://172.17.0.4:8181/restconf/operations/odl-mdsal-lowlevel-control:write-transactions&lt;/a&gt;, data: &amp;lt;input xmlns=&quot;tag:opendaylight.org,2017:controller:yang:lowlevel:control&quot;&amp;gt;&lt;br/&gt;
  &amp;lt;id&amp;gt;prefix-1&amp;lt;/id&amp;gt;&lt;br/&gt;
  &amp;lt;seconds&amp;gt;5&amp;lt;/seconds&amp;gt;&lt;br/&gt;
  &amp;lt;transactions-per-second&amp;gt;10&amp;lt;/transactions-per-second&amp;gt;&lt;br/&gt;
  &amp;lt;chained-transactions&amp;gt;False&amp;lt;/chained-transactions&amp;gt;&lt;br/&gt;
&amp;lt;/input&amp;gt;&lt;/p&gt;

&lt;p&gt;but is not returned after 5 seconds. It timeout out on robot side after 65 seconds.&lt;/p&gt;

&lt;p&gt;The test started around 2017-05-04 10:43:09,965 | INFO  | h for user karaf | command                          | 46 - org.apache.karaf.log.command - 3.0.8 | ROBOT MESSAGE: Starting test Write_Transactions_1_Node&lt;/p&gt;

&lt;p&gt;The particular rest call was around :43:10.216 and expected to finish after 5 seconds. It did not happen.&lt;/p&gt;

&lt;p&gt;Instead there is&lt;/p&gt;

&lt;p&gt;2017-05-04 10:43:31,838 | WARN  | lt-dispatcher-33 | ClusterCoreDaemon                | 201 - com.typesafe.akka.slf4j - 2.4.17 | Cluster Node &lt;span class=&quot;error&quot;&gt;&amp;#91;akka.tcp://opendaylight-cluster-data@172.17.0.4:2550&amp;#93;&lt;/span&gt; - Marking node(s) as UNREACHABLE &lt;span class=&quot;error&quot;&gt;&amp;#91;Member(address = akka.tcp://opendaylight-cluster-data@172.17.0.5:2550, status = Up), Member(address = akka.tcp://opendaylight-cluster-data@172.17.0.6:2550, status = Up)&amp;#93;&lt;/span&gt;. Node roles &lt;span class=&quot;error&quot;&gt;&amp;#91;member-1&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;The system is not under the stress, so i do not really understand why there are akka problems.&lt;/p&gt;


&lt;p&gt;2017-05-04 10:43:12,217 | DEBUG | lt-dispatcher-32 | ShardDataTree                    | 226 - org.opendaylight.controller.sal-distributed-datastore - 1.5.0.SNAPSHOT | member-1-shard-default-config: Preparing transaction member-1-datastore-config-fe-0-txn-10-0&lt;/p&gt;

&lt;p&gt;2017-05-04 10:43:31,823 | DEBUG | lt-dispatcher-32 | CompositeDataTreeCohort          | 226 - org.opendaylight.controller.sal-distributed-datastore - 1.5.0.SNAPSHOT | member-1-datastore-config-fe-0-txn-10-0: canCommit - candidate: &lt;span class=&quot;error&quot;&gt;&amp;#91;FAILED toString()&amp;#93;&lt;/span&gt;&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="26208">CONTROLLER-1654</key>
            <summary>C: write-transactions rpc does not return</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="10004" iconUrl="https://jira.opendaylight.org/images/icons/status_generic.gif" description="">Verified</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="rovarga">Robert Varga</assignee>
                                    <reporter username="pgubka@cisco.com">Peter Gubka</reporter>
                        <labels>
                    </labels>
                <created>Thu, 4 May 2017 11:51:28 +0000</created>
                <updated>Tue, 25 Jul 2023 08:24:33 +0000</updated>
                            <resolved>Tue, 23 May 2017 10:15:26 +0000</resolved>
                                                                    <component>clustering</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="52101" author="pgubka@cisco.com" created="Thu, 4 May 2017 11:51:28 +0000"  >&lt;p&gt;Attachment write_transactions.tar has been added with description: karaf and robot log&lt;/p&gt;</comment>
                            <comment id="52087" author="tpantelis" created="Thu, 4 May 2017 12:44:11 +0000"  >&lt;p&gt;I see a couple of these in the member 1 log:&lt;/p&gt;

&lt;p&gt;safe.akka.slf4j - 2.4.17 | Failed to serialize remote message &lt;span class=&quot;error&quot;&gt;&amp;#91;class org.opendaylight.controller.cluster.access.concepts.RequestEnvelope&amp;#93;&lt;/span&gt; using serializer &lt;span class=&quot;error&quot;&gt;&amp;#91;class akka.serialization.JavaSerializer&amp;#93;&lt;/span&gt;. Transient association error (association remains live)&lt;br/&gt;
akka.remote.MessageSerializer$SerializationException: Failed to serialize remote message &lt;span class=&quot;error&quot;&gt;&amp;#91;class org.opendaylight.controller.cluster.access.concepts.RequestEnvelope&amp;#93;&lt;/span&gt; using serializer &lt;span class=&quot;error&quot;&gt;&amp;#91;class akka.serialization.JavaSerializer&amp;#93;&lt;/span&gt;.&lt;br/&gt;
        at akka.remote.MessageSerializer$.serialize(MessageSerializer.scala:61)&lt;span class=&quot;error&quot;&gt;&amp;#91;210:com.typesafe.akka.remote:2.4.17&amp;#93;&lt;/span&gt;&lt;br/&gt;
...&lt;br/&gt;
Caused by: java.lang.UnsupportedOperationException: Local transaction request CommitLocalTransactionRequest&lt;/p&gt;
{target=member-1-datastore-config-fe-0-txn-10-0, sequence=0, replyTo=Actor[akka://opendaylight-cluster-data/user/$a#-188317460], coordinated=false}
&lt;p&gt; should never be serialized&lt;br/&gt;
        at org.opendaylight.controller.cluster.access.commands.AbstractLocalTransactionRequest.externalizableProxy(AbstractLocalTransactionRequest.java:34)&lt;span class=&quot;error&quot;&gt;&amp;#91;223:org.opendaylight.controller.cds-access-api:1.1.0.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at org.opendaylight.controller.cluster.access.commands.AbstractLocalTransactionRequest.externalizableProxy(AbstractLocalTransactionRequest.java:23)&lt;span class=&quot;error&quot;&gt;&amp;#91;223:org.opendaylight.controller.cds-access-api:1.1.0.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at org.opendaylight.controller.cluster.access.concepts.Request.externalizableProxy(Request.java:27)&lt;span class=&quot;error&quot;&gt;&amp;#91;223:org.opendaylight.controller.cds-access-api:1.1.0.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at org.opendaylight.controller.cluster.access.concepts.Message.writeReplace(Message.java:170)&lt;span class=&quot;error&quot;&gt;&amp;#91;223:org.opendaylight.controller.cds-access-api:1.1.0.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;/p&gt;</comment>
                            <comment id="52088" author="tpantelis" created="Thu, 4 May 2017 12:52:13 +0000"  >&lt;p&gt;member switched from Leader to Follower shortly before the error:&lt;/p&gt;


&lt;p&gt;2017-05-04 10:43:33,364 | INFO  | lt-dispatcher-55 | Shard                            | 219 - org.opendaylight.controller.sal-clustering-commons - 1.5.0.SNAPSHOT | member-1-shard-default-config (Leader) :- Switching from behavior Leader to Follower, election term: 4&lt;/p&gt;

&lt;p&gt;Then the front-end reconnected to the new leader:&lt;/p&gt;

&lt;p&gt;2017-05-04 10:43:42,271 | INFO  | lt-dispatcher-69 | ClientActorBehavior              | 224 - org.opendaylight.controller.cds-access-client - 1.1.0.SNAPSHOT | member-1-frontend-datastore-config: replaced connection ReconnectingClientConnection{client=ClientIdentifier&lt;/p&gt;
{frontend=member-1-frontend-datastore-config, generation=0}, cookie=0, backend=ShardBackendInfo{actor=Actor&lt;a href=&quot;#1279384036&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;akka://opendaylight-cluster-data/user/shardmanager-config/member-1-shard-default-config#1279384036&lt;/a&gt;, sessionId=0, version=BORON, maxMessages=1000, cookie=0, shard=default}} with ConnectedClientConnection{client=ClientIdentifier{frontend=member-1-frontend-datastore-config, generation=0}
&lt;p&gt;, cookie=0, backend=ShardBackendInfo{actor=Actor&lt;span class=&quot;error&quot;&gt;&amp;#91;akka.tcp://opendaylight-cluster-data@172.17.0.5:2550/user/shardmanager-config/member-2-shard-default-config#1531829272&amp;#93;&lt;/span&gt;, sessionId=1, version=BORON, maxMessages=1000, cookie=0, shard=default}}&lt;/p&gt;

&lt;p&gt;It looks like the CommitLocalTransactionRequest was initially targeted to go to the local leader and was retried to go to the new remote leader. It seems like we need to somehow change the local request to a remote one in this case.&lt;/p&gt;</comment>
                            <comment id="52089" author="pgubka@cisco.com" created="Thu, 4 May 2017 13:02:46 +0000"  >&lt;p&gt;(In reply to Tom Pantelis from comment #2)&lt;br/&gt;
&amp;gt; member switched from Leader to Follower shortly before the error:&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; 2017-05-04 10:43:33,364 | INFO  | lt-dispatcher-55 | Shard                  &lt;br/&gt;
&amp;gt; | 219 - org.opendaylight.controller.sal-clustering-commons - 1.5.0.SNAPSHOT&lt;br/&gt;
&amp;gt; | member-1-shard-default-config (Leader) :- Switching from behavior Leader&lt;br/&gt;
&amp;gt; to Follower, election term: 4&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; Then the front-end reconnected to the new leader:&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; 2017-05-04 10:43:42,271 | INFO  | lt-dispatcher-69 | ClientActorBehavior    &lt;br/&gt;
&amp;gt; | 224 - org.opendaylight.controller.cds-access-client - 1.1.0.SNAPSHOT |&lt;br/&gt;
&amp;gt; member-1-frontend-datastore-config: replaced connection&lt;br/&gt;
&amp;gt; ReconnectingClientConnection{client=ClientIdentifier&lt;/p&gt;
{frontend=member-1-
&amp;gt; frontend-datastore-config, generation=0}
&lt;p&gt;, cookie=0,&lt;br/&gt;
&amp;gt; backend=ShardBackendInfo{actor=Actor[akka://opendaylight-cluster-data/user/&lt;br/&gt;
&amp;gt; shardmanager-config/member-1-shard-default-config#1279384036], sessionId=0,&lt;br/&gt;
&amp;gt; version=BORON, maxMessages=1000, cookie=0, shard=default}} with&lt;br/&gt;
&amp;gt; ConnectedClientConnection{client=ClientIdentifier&lt;/p&gt;
{frontend=member-1-frontend-
&amp;gt; datastore-config, generation=0}
&lt;p&gt;, cookie=0,&lt;br/&gt;
&amp;gt; backend=ShardBackendInfo{actor=Actor[akka.tcp://opendaylight-cluster-&lt;br/&gt;
&amp;gt; data@172.17.0.5:2550/user/shardmanager-config/member-2-shard-default-&lt;br/&gt;
&amp;gt; config#1531829272], sessionId=1, version=BORON, maxMessages=1000, cookie=0,&lt;br/&gt;
&amp;gt; shard=default}}&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; It looks like the CommitLocalTransactionRequest was initially targeted to go&lt;br/&gt;
&amp;gt; to the local leader and was retried to go to the new remote leader. It seems&lt;br/&gt;
&amp;gt; like we need to somehow change the local request to a remote one in this&lt;br/&gt;
&amp;gt; case.&lt;/p&gt;

&lt;p&gt;Just want to mention again that write-transaction was called via restconf around 10:43:10.2XX and should have finished within 5-6 seconds time. Time 10:43:09,965 looks too late.&lt;/p&gt;</comment>
                            <comment id="52090" author="rovarga" created="Thu, 4 May 2017 15:26:23 +0000"  >&lt;p&gt;That seems to be a duplicate of &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-1644&quot; title=&quot;tell-based-protocol: attempt to serialize local message&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-1644&quot;&gt;&lt;del&gt;CONTROLLER-1644&lt;/del&gt;&lt;/a&gt;. I&apos;ll take a closer look.&lt;/p&gt;</comment>
                            <comment id="52091" author="tpantelis" created="Thu, 4 May 2017 15:33:38 +0000"  >&lt;p&gt;(In reply to Peter Gubka from comment #3)&lt;br/&gt;
&amp;gt; Just want to mention again that write-transaction was called via restconf&lt;br/&gt;
&amp;gt; around 10:43:10.2XX and should have finished within 5-6 seconds time. Time&lt;br/&gt;
&amp;gt; 10:43:09,965 looks too late.&lt;/p&gt;

&lt;p&gt;Not sure what you mean. I didn&apos;t mention time 10:43:09,965. The leader change occurred at 10:43:33 and the error at 10:43:42 which is later than 10:43:10. The serialization error would&apos;ve timed out the request and failed the transaction.&lt;/p&gt;</comment>
                            <comment id="52092" author="rovarga" created="Thu, 4 May 2017 17:34:20 +0000"  >&lt;p&gt;So this is a standalone transaction facing a local-&amp;gt;remote connect. We definitely should be translating the message from local to remote equivalent.&lt;/p&gt;

&lt;p&gt;Since we do not have debugs, it is not clear if the message was already in the queue or we are facing a late forward (i.e. the transaction was allocated while reconnect was happening). I would assume the request was in the queue and it timed out.&lt;/p&gt;

&lt;p&gt;This is where ProxyHistory$ReconnectCohort.replayRequest() should kick in and route the request to AbstractProxyTransaction.replayRequest(). I will audit the codepaths to see what is going on.&lt;/p&gt;</comment>
                            <comment id="52093" author="rovarga" created="Thu, 4 May 2017 18:11:41 +0000"  >&lt;p&gt;Sorry, that path would be taken by a latecomer request. It seems the trouble lies in RemoteProxyTransaction.handleForwardedRemoteRequest() as it is called from AbstractProxyTransaction.replayMessages(). I will dissect the call paths and untangle the API contract.&lt;/p&gt;</comment>
                            <comment id="52094" author="rovarga" created="Thu, 4 May 2017 22:08:50 +0000"  >&lt;p&gt;There is also another issue in the logs:&lt;/p&gt;

&lt;p&gt;2017-05-04 10:42:19,513 | WARN  | ult-dispatcher-3 | FrontendReadOnlyTransaction      | 226 - org.opendaylight.controller.sal-distributed-datastore - 1.5.0.SNAPSHOT | Rejecting unsupported request TransactionAbortRequest&lt;/p&gt;
{target=member-3-datastore-config-fe-0-txn-0-0, sequence=1, replyTo=Actor[akka.tcp://opendaylight-cluster-data@172.17.0.6:2550/user/$a#-531325700]}

&lt;p&gt;Which looks like a remote request to close a snapshot.&lt;/p&gt;</comment>
                            <comment id="52095" author="pgubka@cisco.com" created="Fri, 5 May 2017 04:26:01 +0000"  >&lt;p&gt;(In reply to Tom Pantelis from comment #5)&lt;br/&gt;
&amp;gt; (In reply to Peter Gubka from comment #3)&lt;br/&gt;
&amp;gt; &amp;gt; Just want to mention again that write-transaction was called via restconf&lt;br/&gt;
&amp;gt; &amp;gt; around 10:43:10.2XX and should have finished within 5-6 seconds time. Time&lt;br/&gt;
&amp;gt; &amp;gt; 10:43:09,965 looks too late.&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; Not sure what you mean. I didn&apos;t mention time 10:43:09,965. The leader&lt;br/&gt;
&amp;gt; change occurred at 10:43:33 and the error at 10:43:42 which is later than&lt;br/&gt;
&amp;gt; 10:43:10. The serialization error would&apos;ve timed out the request and failed&lt;br/&gt;
&amp;gt; the transaction.&lt;/p&gt;

&lt;p&gt;My primary problem which i have is that rpc write-transactions did not return (rest). It started 10:43:10.2XX and should have finished 5-6 seconds later. The leader change (i believe) is just a resulting activity which happened. Just want logs from 10:43:10.2XX not to be overlooked.&lt;/p&gt;</comment>
                            <comment id="52096" author="pgubka@cisco.com" created="Fri, 5 May 2017 04:26:52 +0000"  >&lt;p&gt;(In reply to Robert Varga from comment #9)&lt;br/&gt;
&amp;gt; There is also another issue in the logs:&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; 2017-05-04 10:42:19,513 | WARN  | ult-dispatcher-3 |&lt;br/&gt;
&amp;gt; FrontendReadOnlyTransaction      | 226 -&lt;br/&gt;
&amp;gt; org.opendaylight.controller.sal-distributed-datastore - 1.5.0.SNAPSHOT |&lt;br/&gt;
&amp;gt; Rejecting unsupported request&lt;br/&gt;
&amp;gt; TransactionAbortRequest&lt;/p&gt;
{target=member-3-datastore-config-fe-0-txn-0-0,
&amp;gt; sequence=1,
&amp;gt; replyTo=Actor[akka.tcp://opendaylight-cluster-data@172.17.0.6:2550/user/$a#-
&amp;gt; 531325700]}
&lt;p&gt;&amp;gt; &lt;br/&gt;
&amp;gt; Which looks like a remote request to close a snapshot.&lt;/p&gt;

&lt;p&gt;What debug logs do you want to be on?&lt;/p&gt;</comment>
                            <comment id="52097" author="pgubka@cisco.com" created="Fri, 5 May 2017 10:07:02 +0000"  >&lt;p&gt;Same behavior is in 1node setup. &lt;/p&gt;

&lt;p&gt;Should be reproducible simply.&lt;br/&gt;
1) Start odl with tell-based=true&lt;br/&gt;
2) Make a POST&lt;br/&gt;
http://&amp;lt;ip&amp;gt;:8181/restconf/operations/odl-mdsal-lowlevel-control:write-transactions, &lt;br/&gt;
&amp;lt;input xmlns=&quot;tag:opendaylight.org,2017:controller:yang:lowlevel:control&quot;&amp;gt;&lt;br/&gt;
  &amp;lt;id&amp;gt;prefix-1&amp;lt;/id&amp;gt;&lt;br/&gt;
  &amp;lt;seconds&amp;gt;5&amp;lt;/seconds&amp;gt;&lt;br/&gt;
  &amp;lt;transactions-per-second&amp;gt;10&amp;lt;/transactions-per-second&amp;gt;&lt;br/&gt;
  &amp;lt;chained-transactions&amp;gt;false&amp;lt;/chained-transactions&amp;gt;&lt;br/&gt;
&amp;lt;/input&amp;gt;&lt;/p&gt;

&lt;p&gt;No matter is simple or chained transactions used.&lt;/p&gt;</comment>
                            <comment id="52102" author="pgubka@cisco.com" created="Fri, 5 May 2017 10:07:02 +0000"  >&lt;p&gt;Attachment karaf_log_1.tar.gz.601_simple has been added with description: logs 1node simple&lt;/p&gt;</comment>
                            <comment id="52103" author="pgubka@cisco.com" created="Fri, 5 May 2017 10:07:30 +0000"  >&lt;p&gt;Attachment karaf_log_1.tar.gz.603_chained has been added with description: logs 1node chained&lt;/p&gt;</comment>
                            <comment id="52098" author="pgubka@cisco.com" created="Fri, 5 May 2017 11:42:21 +0000"  >&lt;p&gt;All this above was for module shard test.&lt;/p&gt;

&lt;p&gt;On prefix shard test i run similar test, 1 node odl, rpc produce-transactions&lt;br/&gt;
url: &lt;a href=&quot;http://172.17.0.4:8181/restconf/operations/odl-mdsal-lowlevel-control:produce-transactions&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://172.17.0.4:8181/restconf/operations/odl-mdsal-lowlevel-control:produce-transactions&lt;/a&gt;, data: &amp;lt;input xmlns=&quot;tag:opendaylight.org,2017:controller:yang:lowlevel:control&quot;&amp;gt;&lt;br/&gt;
  &amp;lt;id&amp;gt;prefix-1&amp;lt;/id&amp;gt;&lt;br/&gt;
  &amp;lt;seconds&amp;gt;5&amp;lt;/seconds&amp;gt;&lt;br/&gt;
  &amp;lt;transactions-per-second&amp;gt;10&amp;lt;/transactions-per-second&amp;gt;&lt;br/&gt;
  &amp;lt;isolated-transactions&amp;gt;True&amp;lt;/isolated-transactions&amp;gt;&lt;br/&gt;
&amp;lt;/input&amp;gt;, timeout: 65&lt;/p&gt;

&lt;p&gt;it finished ok, but insted of 5-6 seconds it took 60s to respond correct results to robot. &lt;/p&gt;

&lt;p&gt;And again there is a timeframe when nothing happened for 20s.&lt;br/&gt;
2017-05-05 10:23:58,632 | DEBUG | lt-dispatcher-29 | ShardDataTree                    | 226 - org.opendaylight.controller.sal-distributed-datastore - 1.5.0.SNAPSHOT | member-1-shard-id-ints!-config: Preparing transaction member-1-datastore-Shard-id-ints!-fe-0-chn-5-txn-0-0&lt;br/&gt;
2017-05-05 10:24:17,929 | DEBUG | lt-dispatcher-29 | CompositeDataTreeCohort          | 226 - org.opendaylight.controller.sal-distributed-datastore - 1.5.0.SNAPSHOT | member-1-datastore-Shard-id-ints!-fe-0-chn-5-txn-0-0: canCommit - candidate: &lt;span class=&quot;error&quot;&gt;&amp;#91;FAILED toString()&amp;#93;&lt;/span&gt;&lt;/p&gt;


&lt;p&gt;But finally it responded http status 200 with data {&quot;output&quot;:{&quot;insert-tx&quot;:28,&quot;delete-tx&quot;:21,&quot;all-tx&quot;:49}} around 10:24:56&lt;/p&gt;</comment>
                            <comment id="52104" author="pgubka@cisco.com" created="Fri, 5 May 2017 11:42:21 +0000"  >&lt;p&gt;Attachment karaf_log_1.tar.gz has been added with description: prefix shard produce transactions&lt;/p&gt;</comment>
                            <comment id="52099" author="rovarga" created="Fri, 5 May 2017 11:49:01 +0000"  >&lt;p&gt;The fix for TransactionAbortRequest: &lt;a href=&quot;https://git.opendaylight.org/gerrit/56596&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/56596&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="52100" author="vrpolak" created="Tue, 23 May 2017 10:15:26 +0000"  >&lt;p&gt;Is this a duplicate of &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-1665&quot; title=&quot;C: write-transactions does not return if local leader moved&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-1665&quot;&gt;&lt;del&gt;CONTROLLER-1665&lt;/del&gt;&lt;/a&gt; or was this a different bug with similar symptom?&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="26198">CONTROLLER-1644</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="13664" name="karaf_log_1.tar.gz" size="109587" author="pgubka@cisco.com" created="Fri, 5 May 2017 11:42:21 +0000"/>
                            <attachment id="13662" name="karaf_log_1.tar.gz.601_simple" size="104126" author="pgubka@cisco.com" created="Fri, 5 May 2017 10:07:02 +0000"/>
                            <attachment id="13663" name="karaf_log_1.tar.gz.603_chained" size="103556" author="pgubka@cisco.com" created="Fri, 5 May 2017 10:07:30 +0000"/>
                            <attachment id="13661" name="write_transactions.tar" size="805376" author="pgubka@cisco.com" created="Thu, 4 May 2017 11:51:28 +0000"/>
                    </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>8372</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=8372]]></customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10314"><![CDATA[Carbon-RC1]]></customfieldvalue>

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

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