[CONTROLLER-1507] Entity Ownership Candidates not removed for cluster node which happens to be the an Entity Ownership Shard follower Created: 05/Apr/16  Updated: 19/Sep/16  Resolved: 19/Sep/16

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

Type: Bug
Reporter: Moiz Raja Assignee: Moiz Raja
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: 5656

 Description   

In a 5 node cluster when an entity-ownership shard leader and follower go down simultaneously only the previous leader's candidates are removed from the data when a new leader is elected. This leads to the follower node remaining as candidate even though it is down.

Steps to reproduce,
1. Bring up a 5 node cluster
2. Point an openflow device to all five nodes in the cluster. This should result in a candidate registering for each node in the cluster.
3. Now let's say member-2 is the entity-ownership shard leader
4. Kill the controller process for both member-1 and member-2.
5. After ~10 seconds leadership of the entity-ownership shard should change. At this time check the entity-ownership data using RestConf. You will see that member-1 which still be a candidate for the openflow entity even though member-2 is not.

 Comments   
Comment by Moiz Raja [ 05/Apr/16 ]

https://git.opendaylight.org/gerrit/#/c/37116

Comment by Tom Pantelis [ 19/Sep/16 ]

The patch Moiz submitted was merged a while ago. Also the code has since changed to re-assign owners and not remove candidates for down members on leader change.

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