-
Bug
-
Resolution: Duplicate
-
None
-
None
-
None
-
Operating System: All
Platform: All
-
8643
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
- duplicates
-
CONTROLLER-1738 RequestTimeoutException due to "Shard has no current leader" after shutdown-shard-replica with ShardLeaderStateChanged not delivered
- Confirmed