[
https://issues.apache.org/jira/browse/MESOS-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Mann updated MESOS-1999:
-----------------------------
Description:
Duplicate - see MESOS-1648
At the current time, we use extra tooling around the mesos-slave to create and
manage a pid file for the slave (and master). This tooling is brittle at best,
and it would be very nice if the mesos-slave could create, remove, and manage a
pid file on its own.
In particular, it could use flock(2) to lock the file while it is running,
giving an extra signal to any other slaves starting up that there is a live
mesos-slave currently running (along with kill(2) with signal 0 to probe).
was:
At the current time, we use extra tooling around the mesos-slave to create and
manage a pid file for the slave (and master). This tooling is brittle at best,
and it would be very nice if the mesos-slave could create, remove, and manage a
pid file on its own.
In particular, it could use flock(2) to lock the file while it is running,
giving an extra signal to any other slaves starting up that there is a live
mesos-slave currently running (along with kill(2) with signal 0 to probe).
> mesos slave should handle a PID file
> ------------------------------------
>
> Key: MESOS-1999
> URL: https://issues.apache.org/jira/browse/MESOS-1999
> Project: Mesos
> Issue Type: Bug
> Components: slave
> Reporter: Tobias Weingartner
>
> Duplicate - see MESOS-1648
> At the current time, we use extra tooling around the mesos-slave to create
> and manage a pid file for the slave (and master). This tooling is brittle at
> best, and it would be very nice if the mesos-slave could create, remove, and
> manage a pid file on its own.
> In particular, it could use flock(2) to lock the file while it is running,
> giving an extra signal to any other slaves starting up that there is a live
> mesos-slave currently running (along with kill(2) with signal 0 to probe).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
