先上图哈:
一、Mesos master和slave(其实就是agent)搭建在一台机器上:
过程中遇到两个问题:
1. mesos failed to connect to 5050
I was having the same issues and what fixed it for me was the zookeeper configuration. In my case I was using the EC2 public IP Address rather than the private one. Once I changed the /etc/mesos/zk file to zk://<private IP>:2181/mesos I was able to connect without the constant error messages. In other words, zookeeper was reporting to be running in one IP and mesos-master was trying to connect using a different IP.
https://stackoverflow.com/questions/40641674/mesos-failed-to-connect-error-to-ip5050/43293013
vi /etc/hosts
service zookeeper restart
service mesos-slave restart
service mesos-master restart
service marathon restart
2. Failed to perform recovery: Incompatible agent info detected.
rm -rf /var/log/mesos/*.*
rm -f /var/mesos/meta/slaves/latest
cat /var/log/mesos/mesos-slave.ERROR
root@omi64ub16-dev1:~# ls /var/lib/mesos/meta/slaves/
f09b786a-3e72-44a0-99b5-3ff52bc7f816-S0 latest
root@omi64ub16-dev1:~# rm -rf /var/lib/mesos/meta/slaves/f09b786a-3e72-44a0-99b5-3ff52bc7f816-S0
root@omi64ub16-dev1:~# cat /var/log/mesos/mesos-slave.ERROR
Log file created at: 2017/11/06 22:46:05
Running on machine: omi64ub16-dev1
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
E1106 22:46:05.371798 64416 slave.cpp:6286] EXIT with status 1: Failed to perform recovery: Failed to find latest agent: No such file or directory
To remedy this do as follows:
Step 1: rm -f /var/lib/mesos/meta/slaves/latest
This ensures agent doesn't recover old live executors.
Step 2: Restart the agent.
root@omi64ub16-dev1:~# rm -f /var/lib/mesos/meta/slaves/latest
root@omi64ub16-dev1:~# rm -rf /var/log/mesos/*.*
root@omi64ub16-dev1:~# cat /var/log/mesos/mesos-slave.ERROR
cat: /var/log/mesos/mesos-slave.ERROR: No such file or directory
root@omi64ub16-dev1:~# cat /var/log/mesos/mesos-slave.ERROR
cat: /var/log/mesos/mesos-slave.ERROR: No such file or directory
root@omi64ub16-dev1:~# ls /var/lib/mesos/meta/slaves/
8dc571e3