Oh please yes!
On 13 April 2016 at 08:00, Sam <usultra...@gmail.com> wrote: > +1 > > Sent from my iPhone > > On Apr 13, 2016, at 12:44 PM, Avinash Sridharan <avin...@mesosphere.io> > wrote: > > +1 > > On Tue, Apr 12, 2016 at 9:31 PM, Jie Yu <yujie....@gmail.com> wrote: >> >> +1 >> >> On Tue, Apr 12, 2016 at 9:29 PM, James Peach <jor...@gmail.com> wrote: >> >> > >> > > On Apr 12, 2016, at 3:58 PM, Greg Mann <g...@mesosphere.io> wrote: >> > > >> > > Hey folks! >> > > A number of situations have arisen in which the default value of the >> > Mesos agent `--work_dir` flag (/tmp/mesos) has caused problems on >> > systems >> > in which the automatic cleanup of '/tmp' deletes agent metadata. To >> > resolve >> > this, we would like to eliminate the default value of the agent >> > `--work_dir` flag. You can find the relevant JIRA here. >> > > >> > > We considered simply changing the default value to a more appropriate >> > location, but decided against this because the expected filesystem >> > structure varies from platform to platform, and because it isn't >> > guaranteed >> > that the Mesos agent would have access to the default path on a >> > particular >> > platform. >> > > >> > > Eliminating the default `--work_dir` value means that the agent would >> > exit immediately if the flag is not provided, whereas currently it >> > launches >> > successfully in this case. This will break existing infrastructure which >> > relies on launching the Mesos agent without specifying the work >> > directory. >> > I believe this is an acceptable change because '/tmp/mesos' is not a >> > suitable location for the agent work directory except for short-term >> > local >> > testing, and any production scenario that is currently using this >> > location >> > should be altered immediately. >> > >> > +1 from me too. Defaulting to /tmp just helps people shoot themselves in >> > the foot. >> > >> > J > > > > > -- > Avinash Sridharan, Mesosphere > +1 (323) 702 5245
