Re: Transport endpoint is not connected

Do you mean your zookeeper not in a same private network with master and slave? Maybe you could try set LIBPROCESS_ADVERTISE_IP and LIBPROCESS_ADVERTISE_PORT(could find more details in https://github.com/apache/mesos/blob/master/docs/configuration.md#libprocess-options), but I not have experience f

Re: upgrade from 0.24.1 to 0.25

Hi Craig, it was posted on the marathon email list that 0.11.0 is not safe for production. https://groups.google.com/d/msg/marathon-framework/u4-FKVkh5RQ/wH-s1sdECgAJ From: craig w Sent: Thursday, October 15, 2015 4:13 AM To: user@mesos.apache.org Subject: Re

Re: Transport endpoint is not connected

I figured out the reason. I had configured mesos with internal IPs. I see that Zookeeper broadcasts external network IP to the masters/slaves. There was a firewall issue with the public IP. So that's the problem. Is it the correct way for Zookeeper to broadcast the public IPs? That's understandab

Re: Docker Private Registry problem when update from 0.23 to 0.25

Marathon 0.11.1 + Mesos 0.25.0 + private Docker-Reg (without credentials) works, but with a new error. Marathon (or Mesos) finished each task with an "finished-state" immediately. So let’s wait… https://github.com/mesosphere/marathon/pull/2462#issuecomment-148482471

Re: Docker Private Registry problem when update from 0.23 to 0.25

Hey Brian, sorry for my late response. I'll try the latest 0.11.1. This may be one of the problems: https://github.com/mesosphere/marathon/pull/2415 > Am 15.10.2015 um 21:14 schrieb craig w : > > I've successfully pulled images from a privat

Re: Docker Private Registry problem when update from 0.23 to 0.25

I've successfully pulled images from a private registry using Mesos 0.24.1 and marathon 0.11. I use forcePullImage: true. On Oct 15, 2015 2:25 PM, "Brian Devins" wrote: > Has anyone found some resolution for this? > > I have the mesosphere repo versions of mesos and marathon. 0.24.1 and > 0.11.0

Re: Docker Private Registry problem when update from 0.23 to 0.25

Has anyone found some resolution for this? I have the mesosphere repo versions of mesos and marathon. 0.24.1 and 0.11.0 respectively. I have also tried 0.10.1 for marathon but still no dice. I can manually pull the images if I log into the box. On Wed, Oct 14, 2015 at 2:30 AM, Joachim Andersson <

Transport endpoint is not connected

Hi all, I'm trying to build a mesos cluster with mesosphere 0.25. When I run 3 mesos-master node with QUORUM=2, one is elected as the leader, 1 minute later the leader gives the error messages below, then restarts. Upon restart, they make another election. They keep electing one another in a loop

Re: Is there any APIs for status monitering, how did the Webui got the status of mesos?

the master ui fetch the status.json in 20 second interval 2015-10-08 16:44 GMT+08:00 Marco Massenzio : > Probably the most appropriate endpoint(s) would be something like > http://mesos-master:5050/system/stats.json > http://mesos-master:5050/metrics/snapshot > > for a much more basic 'health' ch

Re: upgrade from 0.24.1 to 0.25

Itamar, Where did you see Marathon 0.11.0 was not ready for production? I ran into this issue (https://github.com/mesosphere/marathon/issues/2369), however, it turned out I just needed to update a configuration parameter. So far, Mesos 0.24.1 and Marathon 0.11.0 are working great. I'm hoping to up

Re: upgrade from 0.24.1 to 0.25

Also note that you're on a problematic Marathon version. I was thinking to upgrade from 0.23&0.10.1 to latest versions, but decided to wait after I saw an announcement on the marathon users list that 0.11 is not recommended for production from last week (Oct 9). I'm waiting until 0.11.1 is out... (

Re: Spark on Mesos / Executor Memory

Resending since user@mesos bounced earlier. My apologies. On Thu, Oct 15, 2015 at 12:19 PM, Bharath Ravi Kumar wrote: > (Reviving this thread since I ran into similar issues...) > > I'm running two spark jobs (in mesos fine grained mode), each belonging to > a different mesos role, say low and h