Are you using DC/OS or "vanilla" Mesos and Marathon, without DC/OS? If you are using Mesos, you might get a better answer on the Mesos mailing list <http://mesos.apache.org/community/#mailing-lists>, and you can also check out these docs on persistent volumes <http://mesos.apache.org/documentation/latest/persistent-volume/>.
Hope this helps! Judith On Thu, Nov 23, 2017 at 1:00 AM, Dino Lokmic <[email protected]> wrote: > I have few machines on Linode and I run Mesos there. Can someone explain > to me, how to set volumes right. > > Now I run taks via marathon like this > > ... > > "constraints": [ > [ > "hostname", > "CLUSTER", > "HOSTNAME" > ] > ], > "container": { > "type": "DOCKER", > "volumes": [ > { > "containerPath": "/opt/storm/storm-local", > "hostPath": "/opt/docker_data/storm/storm-local", > "mode": "RW" > } > ], > "docker": { > "image": "xxxx", > "network": "HOST", > "portMappings": [], > "privileged": false, > "parameters": [], > "forcePullImage": true > } > }, > ... > > So if task is restarted I can be sure it has access to previously used > data. > You can see I have scaling problem and my task is depending on this node. > > I would like for my apps to be node independent and also that they have > redundant data. > > What is best practice for this? > > I want to scale aplication to 2 instances, I1 and I2 > > Instance I1 runs on agent A1 and uses volume V1 > Instance I2 runs on agent A2 and uses volume V2 > > If agent A1 stops, I1 is restared to A3 and uses V1 > If V1 failes I1 uses copy of data from V3... > > > Can someone point to article describing this, or at least give me few > "keywords" > > > Thanks > > > -- Judith Malnick Community Manager 310-709-1517
