Uploaded image for project: 'Marathon'
  1. Marathon
  2. MARATHON-7438

Add a way to remove residual persistent volume data for volumes that no longer exist

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Medium
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Storage Volumes
    • Labels:
    • Zendesk Ticket IDs:
      7016

      Description

      If a cluster's state has been restored from a backup of Marathon data, the new systems will not have the same persistent volumes as the system from which the backup was taken. In this case, Marathon will not allow the services that depended on them to deploy unless the App ID is changed. This workaround has other side effects, such as the need for changes in mesos-dns and navstar-dns that were referring to those apps by ID.

       

      A way to remove the data that Marathon stores for persistent volumes would make the backup restore process much smoother.

        Attachments

          Activity

            People

            • Assignee:
              stevensylvester Steven Sylvester
              Reporter:
              stevensylvester Steven Sylvester
              Team:
              Orchestration Team
              Watchers:
              Matthias Eichstedt, Steven Sylvester
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: