[jira] [Commented] (MESOS-2299) default work_dir of /tmp/mesos is problematic

["Vinod Kone (JIRA)" <ji...@apache.org>]

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

Vinod Kone commented on MESOS-2299:
-----------------------------------

{quote}
Causing problems with task reconciliation
{quote}

What exactly are the problems you are seeing with task reconciliation? A rebooted slave will register as a new slave because after a reboot no tasks will be running. Also, a reboot typically takes longer than the default health check timeout (75s) which causes the master to shutdown the slave.

> default work_dir of /tmp/mesos is problematic
> ---------------------------------------------
>
>                 Key: MESOS-2299
>                 URL: https://issues.apache.org/jira/browse/MESOS-2299
>             Project: Mesos
>          Issue Type: Improvement
>    Affects Versions: 0.20.1
>            Reporter: Lukas Loesche
>            Priority: Trivial
>
> Mesos uses a default of /tmp/mesos if work_dir is not defined.
> This is bad because /tmp on most distros gets wiped upon boot. Therefor when a slave reboots it Registers as a new slave instead of re-registering. Causing problems with task reconciliation.
> A better default following the FHS standard would be /var/tmp/mesos which is the temp that doesn't get wiped at all or in much longer intervals.



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