[ 
https://issues.apache.org/jira/browse/MESOS-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231295#comment-15231295
 ] 

Greg Mann edited comment on MESOS-5064 at 4/7/16 10:59 PM:
-----------------------------------------------------------

After discussing a bit more with Jie, Joris, and BenM, we're going to change 
the agent's {{\-\-work_dir}} flag to have no default value, but remain a 
required field. This means that running the agent binary without specifying 
{{\-\-work_dir}} will fail. While this may break some deployments, we think 
this is acceptable since it's quite unadvisable to be running in production 
with the default agent work directory; best to fail hard now and force users to 
specify a suitable directory that is accessible on their system. I'll send an 
email out to the dev/user lists announcing this plan.


was (Author: greggomann):
After discussing a bit more with Jie, Joris, and BenM, we're going to change 
the agent's {{--work_dir}} flag to have no default value, but remain a required 
field. This means that running the agent binary without specifying 
{{--work_dir}} will fail. While this may break some deployments, we think this 
is acceptable since it's quite unadvisable to be running in production with the 
default agent work directory; best to fail hard now and force users to specify 
a suitable directory that is accessible on their system. I'll send an email out 
to the dev/user lists announcing this plan.

> Document avoiding using `/tmp` as agent’s work directory in production
> ----------------------------------------------------------------------
>
>                 Key: MESOS-5064
>                 URL: https://issues.apache.org/jira/browse/MESOS-5064
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Artem Harutyunyan
>            Assignee: Greg Mann
>
> Following a crash report from the user we need to be more explicit about the 
> dangers of using {{/tmp}} as agent {{work_dir}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to