> > The documentation states "non performance-critical applications" and > "should only be done in a testing or staging environment" about Path type > resources. Is there any particular reason for that?
I think the documentation is not very precise. Path disk resource is the default disk resource, and has been used in prod for years for task's logs and other stuffs in its sandbox. MOUNT disk was introduced mainly for data services which may require disk performance isolation and wants to have exclusive access to a disk. Both of them are definitely ready for production. - Jie On Mon, Nov 21, 2016 at 9:48 AM, Tobias Pfeiffer <t...@preferred.jp> wrote: > Hi, > > I have a Mesos cluster where each node has both SSD and HDD disks, so I > want to offer them separately as described in http://mesos.apache.org/ > documentation/latest/multiple-disk/ > > I am not sure yet where the OS will be installed, but I guess on the disk > that holds the OS I cannot use a Mount type resource, but would have to use > a Path type resource? The documentation states "non performance-critical > applications" and "should only be done in a testing or staging environment" > about Path type resources. Is there any particular reason for that? > > I imagine if I have something like, say, > > / HDD, 1000 GB > /mnt/data SSD, 200 GB > > would it make sense to configure the disk resources like > > { > "resources" : [ > { > "name" : "disk", > "type" : "SCALAR", > "scalar" : { "value" : 800000 }, > "disk" : { > "source" : { > "type" : "PATH", > "path" : { "root" : "/var/lib/mesos-data" } > } > } > }, > { > "name" : "disk", > "type" : "SCALAR", > "scalar" : { "value" : 200000 }, > "disk" : { > "source" : { > "type" : "MOUNT", > "mount" : { "root" : "/mnt/data" } > } > } > } > ] > } > > or is that something that's not suitable for production? > > Thanks, > Tobias > >
