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-1714 controller <p>This is the prefix-based shard version of <a href="https://jira.opendaylight.org/browse/CONTROLLER-1713" title="RequestTimeoutException after remove-shard-replica with &quot;transferred leadership to null&quot;" class="issue-link" data-issue-key="CONTROLLER-1713"><del>CONTROLLER-1713</del></a>.</p> <p>Seen <span class="error">&#91;0&#93;</span> on RelEng first time.<br/> Member-1 was the old leader, member-2 became the new leader.<br/> Similarly to <a href="https://jira.opendaylight.org/browse/CONTROLLER-1705" title="Client on a follower prefix-based shard sometimes does not reconnect when the previous leader is isolated" class="issue-link" data-issue-key="CONTROLLER-1705"><del>CONTROLLER-1705</del></a> (and <a href="https://jira.opendaylight.org/browse/CONTROLLER-1713" title="RequestTimeoutException after remove-shard-replica with &quot;transferred leadership to null&quot;" class="issue-link" data-issue-key="CONTROLLER-1713"><del>CONTROLLER-1713</del></a>), the client on member-1 only attempted to reconnect once (which failed as leadership transfer succeeded only two seconds later).</p> <p>Contrary to <a href="https://jira.opendaylight.org/browse/CONTROLLER-1713" title="RequestTimeoutException after remove-shard-replica with &quot;transferred leadership to null&quot;" class="issue-link" data-issue-key="CONTROLLER-1713"><del>CONTROLLER-1713</del></a>, I see nothing inherently wrong in karaf.log <span class="error">&#91;1&#93;</span> from 07:32:55,200 on.</p> <p><span class="error">&#91;0&#93;</span> <a href="https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/736/log.html.gz#s1-s22-t1-k2-k9" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/736/log.html.gz#s1-s22-t1-k2-k9</a><br/> <span class="error">&#91;1&#93;</span> <a href="https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/736/odl1_karaf.log.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/736/odl1_karaf.log.gz</a></p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1714

RequestTimeoutException after remove-shard-replica (without apparent cause)

Bug Resolved Duplicate Unassigned Vratko Polak Thu, 8 Jun 2017 18:17:07 +0000 Tue, 25 Jul 2023 08:24:43 +0000 Tue, 4 Jul 2017 08:56:30 +0000 clustering 0 1 <p>&gt; I see nothing inherently wrong in karaf.log <span class="error">&#91;1&#93;</span></p> <p>I believe this is a duplicate of <a href="https://jira.opendaylight.org/browse/CONTROLLER-1738" title="RequestTimeoutException due to &quot;Shard has no current leader&quot; after shutdown-shard-replica with ShardLeaderStateChanged not delivered" class="issue-link" data-issue-key="CONTROLLER-1738">CONTROLLER-1738</a>. In the first occasion, we did not see the evidence in log, because "no more dead letters will be logged"</p> <p>2017-06-08 07:33:21,316 | INFO | lt-dispatcher-31 | EmptyLocalActorRef | 174 - com.typesafe.akka.slf4j - 2.4.18 | Message <span class="error">&#91;org.opendaylight.controller.cluster.raft.messages.AppendEntriesReply&#93;</span> from Actor<span class="error">&#91;akka.tcp://opendaylight-cluster-data@10.29.12.177:2550/user/shardmanager-config/member-2-shard-id-ints!-config#-1672771259&#93;</span> to Actor<a href="#854404069" target="_blank" rel="noopener">akka://opendaylight-cluster-data/user/shardmanager-config/member-1-shard-id-ints!-config#854404069</a> was not delivered. <span class="error">&#91;10&#93;</span> dead letters encountered, no more dead letters will be logged. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.</p> Duplicate CONTROLLER-1738 Development External issue ID 8643 External issue URL Issue Type Rank 0|i02s9z: