[CONTROLLER-941] Clustering: DataChangeListeners may not get notified of initial data on registration Created: 17/Oct/14  Updated: 27/Oct/14  Resolved: 27/Oct/14

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

Type: Bug
Reporter: Tom Pantelis Assignee: Tom Pantelis
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: 2210
Priority: Normal

 Description   

DataChangeListeners are only notified if they're on the leader node. The proxy DCL actors don't dispatch notifications to the client DCL until it gets the EnableNotifications message from the shard when it becomes the leader.

After a shard recovers from persistence, it's initialized to a follower and some time can pass before it figures out if it can become the leader. In the meantime, if a client DCL registers, it won't get notified of initial data.

This issue can easily be seen with the toaster.

Potential solution:

On DCL registration, in the Shard, if it isn't the leader, create the DCL actor but don't register with the IMDS until the shard becomes the leader.



 Comments   
Comment by Tom Pantelis [ 21/Oct/14 ]

Submitted https://git.opendaylight.org/gerrit/#/c/12088/

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