[CONTROLLER-1410] After controller reboot, applications don't receive data change notification with the blob of persisted config data Created: 24/Aug/15 Updated: 19/Oct/17 Resolved: 01/Sep/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | clustering |
| Affects Version/s: | Beryllium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Anil Vishnoi | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| External issue ID: | 4179 | ||||||||
| Description |
|
As per my understanding, when controller restarts, application subscribed for data change notification should get a notification with a blob of data that was persisted before the shutdown. OVSDB southbound plugins is not getting the data change notification with the persisted config data after controller reboots. Following are the easy steps that you can use to recreate the issues, but i believe you can try with any yang model and probably see the same issue (although i didn't try it ). 1) git clone https://git.opendaylight.org/gerrit/ovsdb.git 8) wait for all the ovsdb component to come up, you will see "triggerUpdate()" line in the log file. 10) Once you PUT this restconf request, you should see data change dump in the log. Something like this 11) Now reboot the controller and you won't see any dump from data change notificaiton. 12) BUT you will see data still persist in the config data store. You can fire following restconf request to get the data GET: http://localhost:8181/restconf/config/network-topology:network-topology/topology/ovsdb:1 13) This is how we are doing the registration: 14) This is where ovsdb is dumping the data change notification data: I am attaching the log for your reference. karaf.first.start.log – contains log from the first start and adding one entry to config data store Let me know if you need more data or live debug this issue. |
| Comments |
| Comment by Anil Vishnoi [ 24/Aug/15 ] |
|
Attachment karaf.first.start.log has been added with description: Log of first start and config entry addition |
| Comment by Anil Vishnoi [ 24/Aug/15 ] |
|
Attachment karaf.reboot.log has been added with description: Log after reboot |
| Comment by Anil Vishnoi [ 24/Aug/15 ] |
|
I see this issue on both stable/lithium and master branch. |
| Comment by Muthukumaran Kothandaraman [ 25/Aug/15 ] |
|
We see this for specific datastructures on stable/lithium, See this |
| Comment by Anil Vishnoi [ 25/Aug/15 ] |
|
i see this behavior consistently, but i didn't try the same thing for other listener. I see this issue with this listener registration InstanceIdentifier<Node> path = InstanceIdentifier I think |