[CONTROLLER-1252] Clustering: Trim in-memory log on persistence recovery Created: 14/Apr/15 Updated: 07/Jan/16 Resolved: 07/Jan/16 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | clustering |
| Affects Version/s: | Post-Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Tom Pantelis | Assignee: | Tom Pantelis |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 2996 |
| Priority: | Normal |
| Description |
|
At runtime, as state is applied and replicated, we trim the in-memory log to lower the memory footprint. However the persistent log is only trimmed when we do a real snapshot so, on restart, the recovered log will have a larger footprint. It will be trimmed as new state is subsequently applied but we should trim the in-memory log similarly as we're recovering the log. We'll need to persist the replicatedToAllIndex. We should be able include it with the ApplyJournalEntries message. |
| Comments |
| Comment by Moiz Raja [ 17/Nov/15 ] |
|
Does the fix for 3381 address this? If so we can close this one as a duplicate. |