[CONTROLLER-1437] Entity Ownership Service: ownership gets assigned even after candidate registration is closed. Created: 29/Oct/15  Updated: 17/Nov/15  Resolved: 17/Nov/15

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

Type: Bug
Reporter: Kamal Rameshan 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


Attachments: File eos-defect-2.rtf    
External issue ID: 4554

 Description   

This happens when multiple candidates of an entity close their registration at the same time.

The EntityOwnershipListener gets notified with EntityOwnershipChange

{wasOwner=false, isOwner=true, hasOwner=true}

even after the registration for this candidate has been closed.

The listener never gets notified with

{true, false, false}

later.

I was able to reproduce this repeatedly with OF Clustering as it uses EOS.

Logs statements are attached.

In the log, 3 candidates close their registration at the same time (check timestamps).

From the listener Candidate2 gets assigned ownership (i guess intermittently).

But we are notified when it loses its ownership (if at all)



 Comments   
Comment by Kamal Rameshan [ 29/Oct/15 ]

Attachment eos-defect-2.rtf has been added with description: EOS-registartionclose-race-condition

Comment by Kamal Rameshan [ 29/Oct/15 ]

https://bugs.opendaylight.org/show_bug.cgi?id=4554

Affects OF Clustering. Integration tests fail due to this. Needs to be fixed in ODL and OSC.

Comment by Kamal Rameshan [ 29/Oct/15 ]

Please ignore the last comment - accidental push

Comment by Moiz Raja [ 17/Nov/15 ]

https://git.opendaylight.org/gerrit/#/q/message:4554

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