Argh. /etc/hosts was incorrect on the 3rd box. So that's going in
config management now...
On Wed, Jul 2, 2014 at 9:44 PM, Jie Yu wrote:
> Looks like there are only 2 masters:
>
> I0702 20:21:20.772124 14260 network.hpp:461] ZooKeeper group PIDs: {
> log-replica(1)@10.196.106.219:5050, log-repl
Looks like there are only 2 masters:
I0702 20:21:20.772124 14260 network.hpp:461] ZooKeeper group PIDs: {
log-replica(1)@10.196.106.219:5050, log-replica(1)@10.196.106.221:5050 }
The replicated log cannot be initialized unless all the masters are
available.
- Jie
On Wed, Jul 2, 2014 at 1:42 PM
Kevin,
How many masters did you start?
- Jie
On Wed, Jul 2, 2014 at 12:35 PM, Kevin Lyda wrote:
> On Wed, Jul 2, 2014 at 6:45 PM, Kevin Lyda wrote:
> > What should I be hunting down here?
>
> I tried clearing any previous state by removing /tmp/mesos,
> /var/lib/mesos/replicated_log and by r
On Wed, Jul 2, 2014 at 6:45 PM, Kevin Lyda wrote:
> What should I be hunting down here?
I tried clearing any previous state by removing /tmp/mesos,
/var/lib/mesos/replicated_log and by removing the /mesos tree in
zookeeper (delete /mesos/log_replicas and delete /mesos)
The following is in /var/l
Versions: Zookeeper: 3.4.5+dfsg-1
Mesos: 0.19.0 (mesosphere amd64 package for Ubuntu 14.04)
The master is started on each server with this command line:
/usr/local/sbin/mesos-master
--zk=zk://n1.example.com:2181,n2.example.com:2181,n3.example.com:2181/mesos
--port=5050 --cluster="Mesos Cluster" -
