[CONTROLLER-297] Design a knob/throttle for the unbounded Notification queue Created: 08/Apr/14 Updated: 25/Jul/23 Resolved: 12/May/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Kamal Rameshan | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Mac OS |
||
| Description |
|
Currently the notification queue is unbounded. Uunder heavy load or incase the consumer bundle(s) are not resolved, there is potential it to grow and and hog the memory. It would be good to have a safequard menchanism which would pushback the producer and slow down the input rate to the queue. This is also suggested by Robert Varga in the comments for this bug: https://bugs.opendaylight.org/show_bug.cgi?id=645 |
| Comments |
| Comment by Robert Varga [ 31/Oct/14 ] |
|
While not directly introducing a pushback mechanism, https://bugs.opendaylight.org/show_bug.cgi?id=2288 aims to implement APIs which allow us to communicate to applications that we have a congested queue, so they can choose to wait for it to become available, or drop the notification. |
| Comment by Tony Tkacik [ 12/May/15 ] |
|
Notification Queue is replaced with LMAX Disruptor |