Re: removed slace "ID": (131.154.96.172): health check timed out

Actualli the majority of these settings i have already done, out of /etc/mesos-master/ip, here should i write the ip of master interface ? And /etc/mesos-slave/ip, here i should write the ip of slave interface ? Your suggest seems the right one, because if i try to ping some machines from a network

[Breaking Change, MESOS-1865] Redirect to the leader master when current master is not a leader

Hi All, We intend to introduce a breaking change[1] in the http endpoints without the deprecation cycle. For below http endpoints, when user request to a master which is not a leader, user would get a 307 redirect(TEMPORARY_REDIRECT) to the leader master. * /create-volumes * /destroy-volu

Re: removed slace "ID": (131.154.96.172): health check timed out

However i have omitted to say that on these machines is running docker, on some machines docker is running a service on other dont, i saw the docker interface typing ifconfig, i guess this is what you mean Dick Davies? Il 19/apr/2016 09:22, "Stefano Bianchi" ha scritto: > Actualli the majority of

Re: removed slace "ID": (131.154.96.172): health check timed out

Now it seems working. I guess for 2 reasons: 1) I set up /etc/mesos-master/ip and etc/mesos-slave/ip thanks for your suggestion. 2) i added in the routing table the gateway to reach the other network. the second point continue to be strange, since only for 3 machines i had to place the routing rule

Log with warning filling "disk user.log.WARNING.20160416"

Hi, Mesos is creating quite a lot warning log file under /var/log/mesos/archive and it is filling up disk. -rw-r--r-- 1 root root3128 Apr 19 00:00 mesos-fetcher.i**-**-**-*ec2.internal.invalid-user.log.INFO.20160418-163811.16879.1 -rw-r--r-- 1 root root3128 Apr 19 00:00 mesos-fetcher.i*

Re: Log with warning filling "disk user.log.WARNING.20160416"

Have you try use logrotate to manage mesos log? https://github.com/deric/mesos-deb-packaging/blob/master/debian/logrotate On Tue, Apr 19, 2016 at 5:49 PM, Dhiraj Thakur wrote: > Hi, > Mesos is creating quite a lot warning log file > under /var/log/mesos/archive and it is filling up disk. > > -rw

Re: Log with warning filling "disk user.log.WARNING.20160416"

Ok So we need to rotate these log through log rotate? I thought there would be a log rotate option within Mesos. Btw why mesos is creating so many files of same type like INFO? Why doesn't it log all log info under 1 log file? At least for same day? -Dhiraj From: haosdent mailto:haosd...@gmail.c

Re: Log with warning filling "disk user.log.WARNING.20160416"

>Why doesn’t it log all log info under 1 log file? At least for same day? Actually there are from different processes, google glog library use this filename format in log. ``` ...log ``` Unfortunately, google glog didn't provide flags to config this format. On Tue, Apr 19, 2016 at 6:02 PM, Dh

Re: Log with warning filling "disk user.log.WARNING.20160416"

Thanks for info. -Dhiraj From: haosdent mailto:haosd...@gmail.com>> Reply-To: "user@mesos.apache.org" mailto:user@mesos.apache.org>> Date: Tuesday, 19 April 2016 3:46 pm To: user mailto:user@mesos.apache.org>> Subject: Re: Log with warning filling "disk user.log.WARN

Mesos on RHEL 5.X

Hi, When I searched for Mesos rpm for RHEL 5.4, I could not find one. rpms are available only for RHEL 6 and 7. Is there an Mesos 0.28.0 rpm for RHEL 5.4 ? If not has anyone compiled Mesos 0.28.0 on RHEL 5.X successfully ? Thanks in advance, Mani

Re: Mesos on RHEL 5.X

The RHEL5 kernel will not support the necessary bits for mesos. RHEL6 also lacks the overwhelming majority of support for namespaces and control groups. Try upgrading to RHEL7 and then giving Mesos a go. It doesn't support older kernels. On Tuesday, April 19, 2016, Manivannan wrote: > Hi, > > Wh

Re: Mesos on RHEL 5.X

I know someone is still using Mesos in production on RHEL 5.4. You need devtoolset-2 to build Mesos. On Tue, Apr 19, 2016 at 10:50 AM, Jeff Schroeder wrote: > The RHEL5 kernel will not support the necessary bits for mesos. RHEL6 also > lacks the overwhelming majority of support for namespaces an

Re: Mesos on RHEL 5.X

Hi Jeff, Thanks for your reply. We were running mesos 0.18.0 on the boxes with RHEL 5.4 for a long time. We cannot upgrade right away to a newer version of operating system due to several reasons. Hi Jie, Thanks for your reply. Do you know if I can install devtools-2 for RHEL 5.4 using yum ?

Re: Mesos on RHEL 5.X

According to http://linux.web.cern.ch/linux/devtoolset/#install , the steps is wget -O /etc/yum.repos.d/slc5-devtoolset.repo http://linuxsoft.cern.ch/cern/devtoolset/slc5-devtoolset.repo yum install devtoolset-2 On Wed, Apr 20, 2016 at 2:00 AM, Manivannan wrote: > Hi Jeff, > > Thanks for your r

Mesos on RHEL 5.X

Much of the functionality in mesos won't work such as anything using the newer isolation modes using control groups. An example would be: http://mesos.apache.org/documentation/latest/network-monitoring/ I guess it is fraught with dragons. Good luck! On Tuesday, April 19, 2016, Manivannan > wrote:

Re: kafka-mesos still refusing to launch brokers on one cluster

So, I sniffed out the conversation between my working kafka-mesos scheduler and the mesos master, and something I picked up that Wireshark pointed out was that there were 0 server packets in this conversation. So the scheduler is simply POST-ing, and while it’s talking to the socket, it doesn’t

Re: Mesos on RHEL 5.X

Additional problems exist with containers as well. You could also hand roll a kernel upgrade which I've done for some others and this seems to work. However I always make it clear that what you get is "as-is". Kind of like a used car. -Jason > On Apr 19, 2016, at 2:23 PM, Jeff Schroeder > w

Status of Mesos-3821

Hi, I think I encountered the problem described by https://issues.apache.org/jira/browse/MESOS-3821 and wanted to ask if this fix is in Mesos 0.28. But perhaps I misunderstand what's being said; so by way of background our case is Mesos on CentOS 7.2. When we try to set --docker_socket to tcp://:

Re: kafka-mesos still refusing to launch brokers on one cluster

On Tue, Apr 19, 2016 at 11:24 AM, Justin Ryan wrote: > Marathon has no trouble registering a framework and launching jobs on this > cluster, only kafka-mesos. :/ > > Are both these frameworks binding to the same IP/interface? Does anyone of them use any LIBPROCESS_IP or LIBPROCESS_PORT env variab

Re: kafka-mesos still refusing to launch brokers on one cluster

Hiya Vinod, thanks again for chiming in! Both frameworks are indeed binding to the same IP/interface, the kafka-mesos scheduler has LIBPROCESS_IP set, per its’ docs. strace tells me that it tries to connect and then pretty much goes quiet. this socket does show as ESTABLISHED in netstat. — 041

Re: [Proposal] Remove the default value for agent work_dir

It sounds like there's agreement that this is a good idea, so we'll proceed with the patches. Thanks y'all! Greg On Wed, Apr 13, 2016 at 3:39 PM, Justin Ryan wrote: > I’m +1 on removing the default. > > While /opt/mesos may seem reasonable on the surface given many common uses > of /opt, puttin

Re: Mesos on RHEL 5.X

Thanks everyone for your inputs. I was able to compile Mesos 0.27.2 on RHEL 5.4. But Mesos 0.28.1 doesn't compile. I get the below error while running bootstrap : automake: test_http_framework_OBJECTS should not be defined src/Makefile.am:78: while processing program `test-http-framework' src

setting roles in mesos 0.28

I'm confused do roles need to be configured on masters and slaves or just slaves? The docs says --roles has been deprecated on mesos-master but doesn't state an alternate method. on my slaves i'm using default_role='sparkr' and in marathon I've added --mesos_role=sparkr however I'm not ab

Re: setting roles in mesos 0.28

It is not necessary to configure --role on master. Actually it should work if you configure --default_role='sparkr' on agent and start marathon with --mesos_role=sparkr. Which version of mesos are you using? And could you attach the master log? On Wed, Apr 20, 2016 at 11:11 AM, Rodrick Brown wrot

Docker image on mesos-slave

Hi Folks, I have few question related to handling of docker images. Does mesos ever delete older docker images from slave? We push incremental docker image on daily basis image:build_1 and because of that images are piling up on mesos slave. Does mesos offer any option to delete older images?

Re: Docker image on mesos-slave

Mesos don’t handle that part.  We need to have cron job running on mesos slave. -Abhishek On 20-Apr-2016, at 12:02 PM, Dhiraj Thakur wrote: Hi Folks, I have few question related to handling of docker images. Does mesos ever delete older docker

Re: Docker image on mesos-slave

Take a look at https://github.com/spotify/docker-gc , and as Abhishek mentioned, you need to setup a cron job to do this. On Wed, Apr 20, 2016 at 2:32 PM, Dhiraj Thakur wrote: > Hi Folks, > > I have few question related to handling of docker images. > > Does mesos ever delete older docker images

Re: Docker image on mesos-slave

Hi Dhiraj, Have a look at dockergc: https://github.com/spotify/docker-gc That might help you cleaning up old docker images and containers. Kevin > On 20 Apr 2016, at 08:34, Abhishek Amralkar > wrote: > > Mesos don’t handle that part. > We need to have cron job running on mesos slave. > > -

Re: Docker image on mesos-slave

Thanks Guys. I am going to take a look @ docker-gc Can we use it with coreos? -Dhiraj From: Kevin Devroede Sent: Wednesday, April 20, 2016 12:10 PM To: user@mesos.apache.org Subject: Re: Docker image on mesos-slave Hi Dhi