[LISPMAP-104] Expired mappings are not removed from datastore Created: 18/Feb/16 Updated: 19/Oct/17 Resolved: 05/Mar/16 |
|
| Status: | Resolved |
| Project: | lispflowmapping |
| Component/s: | General |
| Affects Version/s: | Beryllium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vina Ermagan | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 5384 |
| Description |
|
After a restart of Karaf, the in memory database is populated from the persisted mappings. Expired mappings are correctly not added to the in memory database, but they still stay in the datastore. Expired mappings should be deleted from the datastore, whenever expiration is detected. |
| Comments |
| Comment by Lori Jakab [ 19/Feb/16 ] |
|
It's more than just when karaf is restarted. Expired mappings in the DAO are lazy-expired when read, but are not deleted from the datastore. |
| Comment by Lori Jakab [ 19/Feb/16 ] |
|
Here's a fix for the Karaf restore part, which is simple: https://git.opendaylight.org/gerrit/#/c/35105/ The general fix is a bit more involved, since we need to avoid "layering violations". |
| Comment by Lori Jakab [ 20/Feb/16 ] |
|
Fix submitted for the runtime part: https://git.opendaylight.org/gerrit/#/c/35122/ |