It sounds like there's agreement that this is a good idea, so we'll proceed
with the patches. Thanks y'all!

Greg

On Wed, Apr 13, 2016 at 3:39 PM, Justin Ryan <[email protected]> wrote:

> I’m +1 on removing the default.
>
> While /opt/mesos may seem reasonable on the surface given many common uses
> of /opt, putting data there doesn’t really comply with FHS.  Arguments
> could be made for /var/mesos (which I’m using) or /srv/mesos, but I think
> no default is fine.
>
> I noticed early on that it was a little odd to default to /tmp, but felt
> as if I was following someone-or-other’s lead.  It’s now clear that’s not
> the case. :)
>
> From: tommy xiao <[email protected]>
> Reply-To: "[email protected]" <[email protected]>
> Date: Tuesday, April 12, 2016 at 11:14 PM
> To: "[email protected]" <[email protected]>
> Cc: dev <[email protected]>
> Subject: Re: [Proposal] Remove the default value for agent work_dir
>
> how about /opt/mesos/
> +1
>
> 2016-04-13 12:44 GMT+08:00 Avinash Sridharan <[email protected]>:
>
>> +1
>>
>> On Tue, Apr 12, 2016 at 9:31 PM, Jie Yu <[email protected]> wrote:
>>
>>> +1
>>>
>>> On Tue, Apr 12, 2016 at 9:29 PM, James Peach <[email protected]> wrote:
>>>
>>> >
>>> > > On Apr 12, 2016, at 3:58 PM, Greg Mann <[email protected]> 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
>>
>
>
>
> --
> Deshi Xiao
> Twitter: xds2000
> E-mail: xiaods(AT)gmail.com
> ------------------------------
>
> P Please consider the environment before printing this e-mail
> The information in this electronic mail message is the sender's
> confidential business and may be legally privileged. It is intended solely
> for the addressee(s). Access to this internet electronic mail message by
> anyone else is unauthorized. If you are not the intended recipient, any
> disclosure, copying, distribution or any action taken or omitted to be
> taken in reliance on it is prohibited and may be unlawful. The sender
> believes that this E-mail and any attachments were free of any virus, worm,
> Trojan horse, and/or malicious code when sent. This message and its
> attachments could have been infected during transmission. By reading the
> message and opening any attachments, the recipient accepts full
> responsibility for taking protective and remedial action about viruses and
> other defects. The sender's employer is not liable for any loss or damage
> arising in any way.
>

Reply via email to