Joseph Wu created MESOS-3180: -------------------------------- Summary: Replicated log (registry) may bloat under some conditions Key: MESOS-3180 URL: https://issues.apache.org/jira/browse/MESOS-3180 Project: Mesos Issue Type: Improvement Components: replicated log Reporter: Joseph Wu
This issue is to track potential problems with the replicated log if it stores diffs without proper compaction/truncation. As part of the [Maintenance Primitives|MESOS-1474] and [Quota|MESOS-1791], the replicated registry will be augmented with additional fields, which may be updates relatively independently. If the replicated log stores diffs, it may store a series of changes: {code} S = info on slaves M = maintenance schedule [X] = a diff containing an update to some part of the registry Registry: [ ] -> [S1] -> [M1] -> [M2] -> [M3] -> [M4] -> ... -> [S2] {code} Between {{S1}} and {{S2}}, multiple {{M}}'s are stored. As each {{M}} is stored, the log cannot truncate the log because the earliest instance of {{S}} is at the beginning. Only once the {{S2}} is reached, does the log get truncated and recover the space used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)