-
Type:
Bug
-
Status: To Do (View Workflow)
-
Priority:
Low
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: VOLTHA v2.10
-
Component/s: onos-olt
-
Labels:None
-
Story Points:5
-
Epic Link:
-
Sprint:VOLTHA 2.10 - Sprint 7
While investigating the failures on https://jenkins.opencord.org/view/VOLTHA-2.X-Tests/job/periodic-voltha-memory-leak-test-bbsim/47/console it appeared that the `volt-remove-subscriber` command slows down overtime (most likely the `volt-add-subscriber` command behaves the same way.
The delay seems to reside between when the CLI command is issued and when the event lands on the queue, for instance:
On the first iteration
<msg timestamp="20220418 13:45:52.202" level="INFO">volt-remove-subscriber-access of:00000a0a0a0a0a0a 256</msg> default/voltha-infra-onos-classic-0[onos-classic]: 13:45:52.221 INFO [Olt] Adding subscriber of:00000a0a0a0a0a0a/256[BBSM000a0001-1] (status: REMOVED, provisionSubscriber: true) to queue: of:00000a0a0a0a0a0a/256[BBSM000a0001-1] with existing []
the robot logs show the command be issued at "13:45:52.202" and the ONOS logs show the event landing in the queue at "13:45:52.221", ~20ms later.
On the 20th iteration
<msg timestamp="20220418 13:54:33.488" level="INFO">volt-remove-subscriber-access of:00000a0a0a0a0a0a 256</msg> default/voltha-infra-onos-classic-0[onos-classic]: 13:54:57.560 INFO [Olt] Adding subscriber of:00000a0a0a0a0a0a/256[BBSM000a0001-1] (status: REMOVED, provisionSubscriber: true) to queue: of:00000a0a0a0a0a0a/256[BBSM000a0001-1] with existing []
the robot logs show the command be issued at "13:54:33.488" and the ONOS logs show the event landing in the queue at "13:54:57.560", ~24s later (note that difference between ms and s).