mesos-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Armand Grillet <agril...@mesosphere.io>
Subject Re: Review Request 64379: Improved logs displayed after a slave failed recovery.
Date Wed, 13 Dec 2017 16:04:06 GMT

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/64379/
-----------------------------------------------------------

(Updated Dec. 13, 2017, 4:04 p.m.)


Review request for mesos, Alexander Rukletsov and Benno Evers.


Changes
-------

Fixed issue.


Bugs: MESOS-8328
    https://issues.apache.org/jira/browse/MESOS-8328


Repository: mesos


Description
-------

Add some steps to clean the Docker daemon
state used by the Docker containerizer.


Diffs (updated)
-----

  src/slave/slave.cpp d997b4272578efffed05d38771f17df387ccac48 


Diff: https://reviews.apache.org/r/64379/diff/3/

Changes: https://reviews.apache.org/r/64379/diff/2-3/


Testing (updated)
-------

New logs:
```
E1213 10:58:10.826020 10057 slave.cpp:6738] EXIT with status 1: Failed to perform recovery:
<error>
If recovery failed due to a change in configuration and you want to
keep the current agent id, you might want to change the
`--reconfiguration_policy` flag to a more permissive value.

To restart this agent with a new agent id instead, do as follows:
rm -f /tmp/agent/meta/slaves/latest
This ensures that the agent does not recover old live executors.

If you were using the docker containerizer, you might want to clear
the docker daemon state. These commands will erase all containers
and images from this host, not just those started by Mesos!
docker kill $(docker ps -q)
docker rm $(docker ps -a -q)
docker rmi $(docker images -q)

Finally, restart the agent.
```


Thanks,

Armand Grillet


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message