[LISPMAP-126] Timestamp being saved to MappingRecord causes excessive datastore activity Created: 09/Aug/16 Updated: 19/Oct/17 Resolved: 24/Aug/16 |
|
| Status: | Resolved |
| Project: | lispflowmapping |
| Component/s: | General |
| Affects Version/s: | Boron |
| 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 |
||
| External issue ID: | 6362 |
| Description |
|
The timestamp is part of the MappingRecord immutable Object, and is being updated with each Map-Register. If the Map-Register cache is not turned on, this causes the datastore to be updated for each Map-Register message. If the Map-Register cache is turned on, the datastore information is not up-to-date. |
| Comments |
| Comment by Lori Jakab [ 09/Aug/16 ] |