[LISPMAP-156] DAO: Empty sub-tables are not removed Created: 18/May/17  Updated: 19/Oct/17  Resolved: 16/Aug/17

Status: Resolved
Project: lispflowmapping
Component/s: Service
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Lori Jakab Assignee: Unassigned
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: 8503
Priority: Low

 Description   

After deleting all mappings or keys in a MapCache, VNI tables remain. This is not a problem per se, but it does make CLI output more cluttered, and objects do take up a small amount of extra memory.

Filed as a lowest priority enhancement issue, just to not loose track.



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

The same applies for empty src/dst sub-entries, updated subject accordingly.

Comment by Vina Ermagan [ 23/May/17 ]

Remaining empty source dest will have logical side effects because a node in radix tree is lingering, interfering with the radix tree algorithms.

Comment by Lori Jakab [ 25/May/17 ]

Fix proposed for master: https://git.opendaylight.org/gerrit/#/c/57799/

Needs cherry-picking to Carbon (and possibly Boron?) once branch is unlocked.

Comment by Lori Jakab [ 16/Aug/17 ]

Carbon cherry-pick https://git.opendaylight.org/gerrit/#/c/58994/

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