https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-1158 controller <p>Currently the in-mem log entries will get removed only if those entries are replicated to ALL the nodes.</p> <p>This is true for both real and fake snapshots.</p> <p>If one of the followers is down, the log would not get cleared causing the system to become unstable.</p> <p>Also during rolling upgrades, if we take a follower down, we do want the rest of the system to function smoothtly.</p> <p>We might want to come with a leader tolerance factor , beyond which the leader would start cleaning the log even if its not replicated to all.</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1158

Clustering:Fix in-mem log cleanup for an Inactive follower

Bug Resolved Done Kamal Rameshan Kamal Rameshan Fri, 13 Feb 2015 19:26:04 +0000 Sat, 21 Feb 2015 13:48:20 +0000 Sat, 21 Feb 2015 13:48:20 +0000 Post-Helium mdsal 0 2 <p><a href="https://git.opendaylight.org/gerrit/#/c/15131/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/15131/</a></p> <p>Currently the simplest fix for this would be to go for the clearing if the memory goes beyond the threshold. Same as the check for Snapshot in RaftActor</p> Development External issue ID 2715 External issue URL Issue Type ODL SR Target Milestone Rank 0|i02ouf: