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

Loosen validation for unreachableStrategy and local persistent volumes


    • Type: Task
    • Status: Accepted
    • Priority: Low
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Storage Volumes
    • Labels:


      As discussed with Tim Harper in this slack conversation (https://mesosphere.slack.com/archives/C1U6FPSTT/p1509958755000146), I would love to loosen the validation for unreachableStrategy and local persistent volumes.

      Currently when trying to use unreachable strategy and local persistent volumes, we get this

      "errors":["unreachableStrategy must be disabled for resident tasks"]

      As far as I can see, this is only a validation issue, but we should also think about deprecating the `residency` property, because it is not needed as we have the explicit unreachable strategy.

      If I want to operate a data store on top of marathon (I want to do it personally and know some users who want to do the same), I would like to use unreachable strategy and local volumes at the same time. You might shoot yourself in the foot, but if you actively configure this, it is the responsibility of the user. I am totally not advocating to change the default of `disabled unreachable strategy` for local persistent volumes, but I would love to make it open to the user.

      Additionally the documentation should be really clear, that this behavior can lead to a situation where you eventually loose data, and that this is only able if you actively set the strategy to something different than the default `disabled`.


          Issue Links



              • Assignee:
                junterstein Johannes Unterstein
                Orchestration Team
                Alena Varkockova, Johannes Unterstein, Matthias Eichstedt, Tim Harper
              • Watchers:
                4 Start watching this issue


                • Created: