Comment 7 for bug 1425415
Revision history for this message
| OpenContrail Admin (ci-admin-f) wrote A change has been merged | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Reviewed: https:/
Committed: http://
Submitter: Zuul
Branch: master
commit 3609f2d3bce5581
Author: ashoksingh <email address hidden>
Date: Sat Feb 21 23:11:25 2015 +0530
In scaled scenario reduce the number of prouter UVEs sent from agent
In Scaled setup, it is observed that agent spends lot of time sending UVEs. One of the issues identified is when multiple DB change notifications are received, agent ends up building and sending multiple prouter UVE messages (one for each change notification). To avoid building prouter UVE message for each change notification, agent now builds prouter UVE message only if we have not already enqueued request to build the prouter UVE. This helps us in achieving state compression. This is achieved using TaskTrigger. With these changes it was observed that agent starts about ~35 seconds faster than it would have without these changes.
Partial-Bug: #1424218
(cherry picked from commit 714103efe78012b
Fix Agent crash in UVE code when out of order deletes are received.
Crash was happening because we were accessing an object pointer after it was deleted. As a fix we no longer store any object pointers in UVE data-structures. Instead store the required data in UVE data-structures.
Closes-Bug: #1425415
(cherry picked from commit dcd844e7a8930af
Change-Id: I50fe8dd1eea493