I tested the command and it works. Thanks!
On Fri, Mar 24, 2017 at 2:24 AM, Benjamin Mahler wrote:
> I would recommend avoiding a manual clean up of the work directory, since
> it's not guaranteed that this approach will remain correct as things
> evolve. To have the agent perform the cleanup us
I would recommend avoiding a manual clean up of the work directory, since
it's not guaranteed that this approach will remain correct as things
evolve. To have the agent perform the cleanup using its own logic, you can
run:
mesos-agent --recover=cleanup --work_dir= --master=
Also, there is already
Thank you. I will do that then.
Mike
On Wed, Mar 22, 2017 at 6:57 PM, Tomek Janiszewski
wrote:
> 1. Cleanup in required when agent configuration is not compatible with
> previous version. This mean task runtime change. This occurs when:
> resources, isolators, attributes or containerizers chang
1. Cleanup in required when agent configuration is not compatible with
previous version. This mean task runtime change. This occurs when:
resources, isolators, attributes or containerizers change.
2. IMO it's OK. When you reboot node all its tasks are gone so you won't
lose anything. Node will be r
Hi everybody,
I'm having troubles with the cleanup of the mesos agent work directory.
When we change some configuration parameters to the agent (e.g. the
--resource flag), the agent refuses to start and asks the removal of
*/var/lib/mesos-agent/meta/slaves/latest* in the logs.
Since we are automa
5 matches
Mail list logo
