[CONTROLLER-1714] RequestTimeoutException after remove-shard-replica (without apparent cause) Created: 08/Jun/17  Updated: 25/Jul/23  Resolved: 04/Jul/17

Status: Resolved
Project: controller
Component/s: clustering
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Vratko Polak Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Issue Links:
Duplicate
duplicates CONTROLLER-1738 RequestTimeoutException due to "Shard... Confirmed
External issue ID: 8643

 Description   

This is the prefix-based shard version of CONTROLLER-1713.

Seen [0] on RelEng first time.
Member-1 was the old leader, member-2 became the new leader.
Similarly to CONTROLLER-1705 (and CONTROLLER-1713), the client on member-1 only attempted to reconnect once (which failed as leadership transfer succeeded only two seconds later).

Contrary to CONTROLLER-1713, I see nothing inherently wrong in karaf.log [1] from 07:32:55,200 on.

[0] https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/736/log.html.gz#s1-s22-t1-k2-k9
[1] https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/736/odl1_karaf.log.gz

 Comments   
Comment by Vratko Polak [ 04/Jul/17 ]

> I see nothing inherently wrong in karaf.log [1]

I believe this is a duplicate of CONTROLLER-1738. In the first occasion, we did not see the evidence in log, because "no more dead letters will be logged"

2017-06-08 07:33:21,316 | INFO | lt-dispatcher-31 | EmptyLocalActorRef | 174 - com.typesafe.akka.slf4j - 2.4.18 | Message [org.opendaylight.controller.cluster.raft.messages.AppendEntriesReply] from Actor[akka.tcp://opendaylight-cluster-data@10.29.12.177:2550/user/shardmanager-config/member-2-shard-id-ints!-config#-1672771259] to Actorakka://opendaylight-cluster-data/user/shardmanager-config/member-1-shard-id-ints!-config#854404069 was not delivered. [10] 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'.

Generated at Wed Feb 07 19:56:16 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.