Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-3180

Replicated log (registry) may bloat under some conditions

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Accepted
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: replicated log

      Description

      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 and Quota, 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:

      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]
      

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                kaysoky Joseph Wu
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: