[CONTROLLER-1705] Client on a follower prefix-based shard sometimes does not reconnect when the previous leader is isolated Created: 06/Jun/17  Updated: 25/Jul/23  Resolved: 18/Sep/17

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

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

Operating System: All
Platform: All

External issue ID: 8605

 Description   

This has been seen on Sandbox [0] when testing for a fix [1]. Member-1 was the original leader, after isolation member-2 became the new leader, but the producer has failed on member-3.

CONTROLLER-1704 symptom is visible from Robot and CONTROLLER-1702 symptom is visible in karaf.log [2] of member-3, but there may be more clues between 07:07:04,481 and 07:09:30,875.

[0] https://logs.opendaylight.org/sandbox/jenkins091/controller-csit-3node-clustering-only-carbon/4/log.html.gz#s1-s12-t3-k2-k25-k1-k8
[1] https://git.opendaylight.org/gerrit/#/c/58194/3
[2] https://logs.opendaylight.org/sandbox/jenkins091/controller-csit-3node-clustering-only-carbon/4/odl3_karaf.log.gz
Generated at Wed Feb 07 19:56:14 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.