Re: Documentation about debugging mesos-master : newbie

Hi Vinit, Please check if you are encountering this issue: https://github.com/Homebrew/homebrew-dupes/issues/221 Thanks, Guangya On Fri, Jun 3, 2016 at 2:24 AM, Vinit Mahedia wrote: > Hi Gilbert, > > Thank you for replying. > > Yes, I did that. > > >1.

Re: Documentation about debugging mesos-master : newbie

I tried that I am getting a linking error; I guess it just does not like me or it's not my day. There's a psychic across the road, I think he may earn some money today. libtool: link: `slave/libmesos_no_3rdparty_la-validation.lo' is not a valid libtool object Anyway, just to give you a bit more

Re: Documentation about debugging mesos-master : newbie

For dev, I would strongly recommend using linux os (e.g., ubuntu14.04, 15.10, centos7.1, etc.). Because features are very limited in os x, most of features like using containers, cgroup isolation etc. you will need a linux environment. PS: using a vagrant box may be convenient to setup env on

Re: Documentation about debugging mesos-master : newbie

I tried that, it did not help either, same error. What do you use for dev OS, IDE etc. Do you think switching on ubuntu should help? I will try that anyway. I am out of ideas at this point if switching OS does not work either. gdb) b master.cpp:2481 Cannot access memory at address 0x714d40 On

Re: Documentation about debugging mesos-master : newbie

Vinit, Seems like your question is similar to this one: https://mail-archives.apache.org/mod_mbox/mesos-dev/201507.mbox/%3CCAOs_uxyyeJNF+CtceOd7zZabSMJTneC=yyqcpwbz-gjyesp...@mail.gmail.com%3E Could you verify if James' reply would help for your case?

Mesos 0.24.1 on Raspberry Pi 3

FYI, based on the work others have done in the past, Netflix was able to get Mesos agent building and running on Raspberry Pi natively and under Docker containers. Please see this blog for the information: bit.ly/TitusOnPi -- Andrew Spyker (aspy...@netflix.com) Twitter: @aspyker Blog:

Re: Documentation about debugging mesos-master : newbie

Hi Gilbert, Thank you for replying. Yes, I did that. 1. ./configure --enable-debug --disable-java --disable-python 2. make 3. ./bin/gdb-mesos-master.sh --ip=127.0.0.1 --work_dir=. Although even after setting source directory, I can not set breakpoint I get warning like this (gdb)

Re: Documentation about debugging mesos-master : newbie

Hi Vinit, Did you configure with debug mode (e.g., ../confugure --enable-debug)? Assuming you have the gdb installed, you should be able to debug mesos master in gbd: ./bin/gdb-mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos Gilbert On Thu, Jun 2, 2016 at 9:30 AM, Vinit Mahedia

Documentation about debugging mesos-master : newbie

I have been trying to debug mesos-master using gdb-mesos-master.sh although it does not load symbols or sources. I tried to set those paths as well but since it thinks mesos-master, libtool script, is the main binary. I just want to set the dev environment and try to fix a very stupid bug to

Re: CMake and CLion

Hey folks. Sorry about getting back to this so late. I've been out of country for about 2.5 weeks, and we've been trying to make sure all the Windows patches land in Mesos 1.0. Just a quick note, the Windows MVP commit brings the CMake build system much closer to being a viable alternative to

Re: Completed executors presented as alive

Yes. I see dead executor in executors. It's tasks and queued_tasks are empty but there is one task in completed_tasks. frameworks.completed_executors are filled with other executors. czw., 2.06.2016 o 15:39 użytkownik haosdent napisał: > Hi, @janiszt Seems the completed

Re: Completed executors presented as alive

Hi, @janiszt Seems the completed executors only exists in completed_frameworks.completed_executors or frameworks.completed_executors in my side. In your side, does completed_executors exists in any other fields? On Thu, Jun 2, 2016 at 5:39 PM, Tomek Janiszewski wrote: > Hi >

Completed executors presented as alive

Hi I'm running Mesos 0.28.0. Mesos slave(1)/state endpoint returns some completed executors not in frameworks.completed_executors but in frameworks. executors. Is it normal behavior? How to force Mesos to move completed executors into frameworks.executors? Thanks Tomek