Clean summary cache on node up and summary #1144
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes the issue where sometime the summary cache was not properly cleaned and so could create a summary with 2 summary inside.
Now 2 summary backup are kept, the current one and the previous one.
The previous summary slots in ets table are cleared right after being uses by subset.
On event node_up, backup file and ets table is cleaned.
Fixes #1138
Type of change
How Has This Been Tested?
Unit test
Runned 2 nodes, send to one a node_down event before a summary and send a node_up after the summary, ets table is cleaned as expected.
Checklist: