[LISPMAP-171] Karaf CLI commands should trigger expired mapping removal Created: 18/Oct/17  Updated: 28/Nov/17  Resolved: 28/Nov/17

Status: Verified
Project: lispflowmapping
Component/s: Service
Affects Version/s: Oxygen
Fix Version/s: Oxygen, Nitrogen-SR2, Carbon-SR3

Type: Bug
Reporter: Lori Jakab Assignee: Lori Jakab
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: 9311
Priority: Normal

 Description   

Lazy removal of a southbound originated mapping is triggered when a lookup for that particular mapping is performed. Additionally, on a Map-Register, the time bucket wheel for mapping removal is ran for all mappings. However, if a mapping expires and no such event happens, mappings are still kept in the map-cache, and shown when listed from the Karaf console. It would be much better to run the time bucket wheel algorithm before listing mappings in the Karaf console.



 Comments   
Comment by Lori Jakab [ 18/Oct/17 ]

Fix proposed: https://git.opendaylight.org/gerrit/#/c/64441/

Generated at Wed Feb 07 20:06:40 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.