You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by Greg Mann <gr...@mesosphere.io> on 2016/04/13 00:58:47 UTC
[Proposal] Remove the default value for agent work_dir
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
<https://issues.apache.org/jira/browse/MESOS-5064>.
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.
If you have any thoughts/opinions/concerns regarding this change, please
let us know!
Cheers,
Greg
Re: [Proposal] Remove the default value for agent work_dir
Posted by June Taylor <ju...@umn.edu>.
+1
As a new user this was one of the first things we changed, to direct Mesos
to use a volume with more disk space. Please print a useful error message
to the logs, though.
Thanks,
June Taylor
System Administrator, Minnesota Population Center
University of Minnesota
On Tue, Apr 12, 2016 at 5:58 PM, Greg Mann <gr...@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
> <https://issues.apache.org/jira/browse/MESOS-5064>.
>
> 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.
>
> If you have any thoughts/opinions/concerns regarding this change, please
> let us know!
>
> Cheers,
> Greg
>
Re: [Proposal] Remove the default value for agent work_dir
Posted by Timothy Chen <tn...@gmail.com>.
+1
Tim
On Wed, Apr 13, 2016 at 5:31 AM, Jie Yu <yu...@gmail.com> wrote:
> +1
>
> On Tue, Apr 12, 2016 at 9:29 PM, James Peach <jo...@gmail.com> wrote:
>
>>
>> > On Apr 12, 2016, at 3:58 PM, Greg Mann <gr...@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
Re: [Proposal] Remove the default value for agent work_dir
Posted by Dick Davies <di...@hellooperator.net>.
Oh please yes!
On 13 April 2016 at 08:00, Sam <us...@gmail.com> wrote:
> +1
>
> Sent from my iPhone
>
> On Apr 13, 2016, at 12:44 PM, Avinash Sridharan <av...@mesosphere.io>
> wrote:
>
> +1
>
> On Tue, Apr 12, 2016 at 9:31 PM, Jie Yu <yu...@gmail.com> wrote:
>>
>> +1
>>
>> On Tue, Apr 12, 2016 at 9:29 PM, James Peach <jo...@gmail.com> wrote:
>>
>> >
>> > > On Apr 12, 2016, at 3:58 PM, Greg Mann <gr...@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
Re: [Proposal] Remove the default value for agent work_dir
Posted by Sam <us...@gmail.com>.
+1
Sent from my iPhone
> On Apr 13, 2016, at 12:44 PM, Avinash Sridharan <av...@mesosphere.io> wrote:
>
> +1
>
>> On Tue, Apr 12, 2016 at 9:31 PM, Jie Yu <yu...@gmail.com> wrote:
>> +1
>>
>> On Tue, Apr 12, 2016 at 9:29 PM, James Peach <jo...@gmail.com> wrote:
>>
>> >
>> > > On Apr 12, 2016, at 3:58 PM, Greg Mann <gr...@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
Re: [Proposal] Remove the default value for agent work_dir
Posted by Jörg Schad <jo...@mesosphere.io>.
+1 Thanks for doing this!
On Tue, Apr 19, 2016 at 11:33 PM, Greg Mann <gr...@mesosphere.io> wrote:
> 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 <ju...@ziprealty.com> 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 <xi...@gmail.com>
>> Reply-To: "user@mesos.apache.org" <us...@mesos.apache.org>
>> Date: Tuesday, April 12, 2016 at 11:14 PM
>> To: "user@mesos.apache.org" <us...@mesos.apache.org>
>> Cc: dev <de...@mesos.apache.org>
>> 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 <av...@mesosphere.io>:
>>
>>> +1
>>>
>>> On Tue, Apr 12, 2016 at 9:31 PM, Jie Yu <yu...@gmail.com> wrote:
>>>
>>>> +1
>>>>
>>>> On Tue, Apr 12, 2016 at 9:29 PM, James Peach <jo...@gmail.com> wrote:
>>>>
>>>> >
>>>> > > On Apr 12, 2016, at 3:58 PM, Greg Mann <gr...@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
>>>
>>
>>
>>
>> --
>> 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.
>>
>
>
Re: [Proposal] Remove the default value for agent work_dir
Posted by Greg Mann <gr...@mesosphere.io>.
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 <ju...@ziprealty.com> 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 <xi...@gmail.com>
> Reply-To: "user@mesos.apache.org" <us...@mesos.apache.org>
> Date: Tuesday, April 12, 2016 at 11:14 PM
> To: "user@mesos.apache.org" <us...@mesos.apache.org>
> Cc: dev <de...@mesos.apache.org>
> 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 <av...@mesosphere.io>:
>
>> +1
>>
>> On Tue, Apr 12, 2016 at 9:31 PM, Jie Yu <yu...@gmail.com> wrote:
>>
>>> +1
>>>
>>> On Tue, Apr 12, 2016 at 9:29 PM, James Peach <jo...@gmail.com> wrote:
>>>
>>> >
>>> > > On Apr 12, 2016, at 3:58 PM, Greg Mann <gr...@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
>>
>
>
>
> --
> 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.
>
Re: [Proposal] Remove the default value for agent work_dir
Posted by Greg Mann <gr...@mesosphere.io>.
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 <ju...@ziprealty.com> 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 <xi...@gmail.com>
> Reply-To: "user@mesos.apache.org" <us...@mesos.apache.org>
> Date: Tuesday, April 12, 2016 at 11:14 PM
> To: "user@mesos.apache.org" <us...@mesos.apache.org>
> Cc: dev <de...@mesos.apache.org>
> 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 <av...@mesosphere.io>:
>
>> +1
>>
>> On Tue, Apr 12, 2016 at 9:31 PM, Jie Yu <yu...@gmail.com> wrote:
>>
>>> +1
>>>
>>> On Tue, Apr 12, 2016 at 9:29 PM, James Peach <jo...@gmail.com> wrote:
>>>
>>> >
>>> > > On Apr 12, 2016, at 3:58 PM, Greg Mann <gr...@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
>>
>
>
>
> --
> 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.
>
Re: [Proposal] Remove the default value for agent work_dir
Posted by Justin Ryan <ju...@ziprealty.com>.
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 <xi...@gmail.com>>
Reply-To: "user@mesos.apache.org<ma...@mesos.apache.org>" <us...@mesos.apache.org>>
Date: Tuesday, April 12, 2016 at 11:14 PM
To: "user@mesos.apache.org<ma...@mesos.apache.org>" <us...@mesos.apache.org>>
Cc: dev <de...@mesos.apache.org>>
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 <av...@mesosphere.io>>:
+1
On Tue, Apr 12, 2016 at 9:31 PM, Jie Yu <yu...@gmail.com>> wrote:
+1
On Tue, Apr 12, 2016 at 9:29 PM, James Peach <jo...@gmail.com>> wrote:
>
> > On Apr 12, 2016, at 3:58 PM, Greg Mann <gr...@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<tel:%2B1%20%28323%29%20702%205245>
--
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com<http://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.
Re: [Proposal] Remove the default value for agent work_dir
Posted by tommy xiao <xi...@gmail.com>.
how about /opt/mesos/
+1
2016-04-13 12:44 GMT+08:00 Avinash Sridharan <av...@mesosphere.io>:
> +1
>
> On Tue, Apr 12, 2016 at 9:31 PM, Jie Yu <yu...@gmail.com> wrote:
>
>> +1
>>
>> On Tue, Apr 12, 2016 at 9:29 PM, James Peach <jo...@gmail.com> wrote:
>>
>> >
>> > > On Apr 12, 2016, at 3:58 PM, Greg Mann <gr...@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
>
--
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com
Re: [Proposal] Remove the default value for agent work_dir
Posted by tommy xiao <xi...@gmail.com>.
how about /opt/mesos/
+1
2016-04-13 12:44 GMT+08:00 Avinash Sridharan <av...@mesosphere.io>:
> +1
>
> On Tue, Apr 12, 2016 at 9:31 PM, Jie Yu <yu...@gmail.com> wrote:
>
>> +1
>>
>> On Tue, Apr 12, 2016 at 9:29 PM, James Peach <jo...@gmail.com> wrote:
>>
>> >
>> > > On Apr 12, 2016, at 3:58 PM, Greg Mann <gr...@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
>
--
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com
Re: [Proposal] Remove the default value for agent work_dir
Posted by Avinash Sridharan <av...@mesosphere.io>.
+1
On Tue, Apr 12, 2016 at 9:31 PM, Jie Yu <yu...@gmail.com> wrote:
> +1
>
> On Tue, Apr 12, 2016 at 9:29 PM, James Peach <jo...@gmail.com> wrote:
>
> >
> > > On Apr 12, 2016, at 3:58 PM, Greg Mann <gr...@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
Re: [Proposal] Remove the default value for agent work_dir
Posted by Avinash Sridharan <av...@mesosphere.io>.
+1
On Tue, Apr 12, 2016 at 9:31 PM, Jie Yu <yu...@gmail.com> wrote:
> +1
>
> On Tue, Apr 12, 2016 at 9:29 PM, James Peach <jo...@gmail.com> wrote:
>
> >
> > > On Apr 12, 2016, at 3:58 PM, Greg Mann <gr...@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
Re: [Proposal] Remove the default value for agent work_dir
Posted by Timothy Chen <tn...@gmail.com>.
+1
Tim
On Wed, Apr 13, 2016 at 5:31 AM, Jie Yu <yu...@gmail.com> wrote:
> +1
>
> On Tue, Apr 12, 2016 at 9:29 PM, James Peach <jo...@gmail.com> wrote:
>
>>
>> > On Apr 12, 2016, at 3:58 PM, Greg Mann <gr...@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
Re: [Proposal] Remove the default value for agent work_dir
Posted by Jie Yu <yu...@gmail.com>.
+1
On Tue, Apr 12, 2016 at 9:29 PM, James Peach <jo...@gmail.com> wrote:
>
> > On Apr 12, 2016, at 3:58 PM, Greg Mann <gr...@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
Re: [Proposal] Remove the default value for agent work_dir
Posted by Jie Yu <yu...@gmail.com>.
+1
On Tue, Apr 12, 2016 at 9:29 PM, James Peach <jo...@gmail.com> wrote:
>
> > On Apr 12, 2016, at 3:58 PM, Greg Mann <gr...@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
Re: [Proposal] Remove the default value for agent work_dir
Posted by James Peach <jo...@gmail.com>.
> On Apr 12, 2016, at 3:58 PM, Greg Mann <gr...@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
Re: [Proposal] Remove the default value for agent work_dir
Posted by Klaus Ma <kl...@gmail.com>.
+1
----
Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer
Platform OpenSource Technology, STG, IBM GCG
+86-10-8245 4084 | klaus1982.cn@gmail.com | http://k82.me
On Wed, Apr 13, 2016 at 11:14 PM, Paul <ar...@gmail.com> wrote:
> +1
>
> On Apr 13, 2016, at 11:01 AM, Ken Sipe <ke...@gmail.com> wrote:
>
> +1
>
> On Apr 12, 2016, at 5:58 PM, Greg Mann <gr...@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
> <https://issues.apache.org/jira/browse/MESOS-5064>.
>
> 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.
>
> If you have any thoughts/opinions/concerns regarding this change, please
> let us know!
>
> Cheers,
> Greg
>
>
>
Re: [Proposal] Remove the default value for agent work_dir
Posted by Klaus Ma <kl...@gmail.com>.
+1
----
Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer
Platform OpenSource Technology, STG, IBM GCG
+86-10-8245 4084 | klaus1982.cn@gmail.com | http://k82.me
On Wed, Apr 13, 2016 at 11:14 PM, Paul <ar...@gmail.com> wrote:
> +1
>
> On Apr 13, 2016, at 11:01 AM, Ken Sipe <ke...@gmail.com> wrote:
>
> +1
>
> On Apr 12, 2016, at 5:58 PM, Greg Mann <gr...@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
> <https://issues.apache.org/jira/browse/MESOS-5064>.
>
> 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.
>
> If you have any thoughts/opinions/concerns regarding this change, please
> let us know!
>
> Cheers,
> Greg
>
>
>
Re: [Proposal] Remove the default value for agent work_dir
Posted by Paul <ar...@gmail.com>.
+1
> On Apr 13, 2016, at 11:01 AM, Ken Sipe <ke...@gmail.com> wrote:
>
> +1
>> On Apr 12, 2016, at 5:58 PM, Greg Mann <gr...@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.
>>
>> If you have any thoughts/opinions/concerns regarding this change, please let us know!
>>
>> Cheers,
>> Greg
>
Re: [Proposal] Remove the default value for agent work_dir
Posted by Ken Sipe <ke...@gmail.com>.
+1
> On Apr 12, 2016, at 5:58 PM, Greg Mann <gr...@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 <https://issues.apache.org/jira/browse/MESOS-5064>.
>
> 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.
>
> If you have any thoughts/opinions/concerns regarding this change, please let us know!
>
> Cheers,
> Greg
Re: [Proposal] Remove the default value for agent work_dir
Posted by Zameer Manji <zm...@apache.org>.
+1
I have seen this confuse many users of Apache Aurora many times.
Eliminating the default will cause operators to select a location with the
appropriate persistence properties.
On Tue, Apr 12, 2016 at 3:58 PM, Greg Mann <gr...@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
> <https://issues.apache.org/jira/browse/MESOS-5064>.
>
> 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.
>
> If you have any thoughts/opinions/concerns regarding this change, please
> let us know!
>
> Cheers,
> Greg
>
> --
> Zameer Manji
>
>
Re: [Proposal] Remove the default value for agent work_dir
Posted by James Peach <jo...@gmail.com>.
> On Apr 12, 2016, at 3:58 PM, Greg Mann <gr...@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
Re: [Proposal] Remove the default value for agent work_dir
Posted by Ken Sipe <ke...@gmail.com>.
+1
> On Apr 12, 2016, at 5:58 PM, Greg Mann <gr...@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 <https://issues.apache.org/jira/browse/MESOS-5064>.
>
> 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.
>
> If you have any thoughts/opinions/concerns regarding this change, please let us know!
>
> Cheers,
> Greg