You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by Adam Monsen <ha...@gmail.com> on 2013/05/29 18:53:49 UTC

user seeking help on #mesos

Someone (Cc'd) is asking for help in #mesos (on Freenode). Is anyone
available to stop by and answer a couple of questions?

> [09:48] < jeid> I just had some questions about config files.
> [09:48] < jeid> I think the github docs are out of date.
> [09:48] < jeid> And aren't really helpful.
> [09:49] < jeid> I have hot-master and all my slaves working with
> zookeeper
> [09:49] < jeid> however I start all of my services by hand
> [09:49] < jeid> doing ./mesos-master
> --zk=zk://zookeeper1:2181,zk2:2181/mesos
> [09:49] < jeid> I want to specify that zookeeper option somewhere
> but the docs don't specify it anywhere.
> [09:49] < jeid> so I just want to do ./mesos-daemon
> [09:50] < jeid> in the future.

Re: user seeking help on #mesos

Posted by Vinod Kone <vi...@gmail.com>.
What is your cluster setup like?


On Wed, May 29, 2013 at 11:34 AM, Eid, Julien <Ju...@vimeo.com> wrote:

> Okay, I'll use the active config way to configure it. I also seem to get
> this weird bug where my slaves can't connect to the masters. It appears to
> detect a master running on localhost even though there is none, then
> disconnects, and is unable to find any other masters using zookeeper.
>
> 2013-05-29 14:28:54,952:9122(0x7fded8cff700):ZOO_DEBUG@process_completions@1795:
> Calling COMPLETION_STRINGLIST for xid=0x51a648e8 rc=0
> I0529 14:28:54.952693  9136 detector.cpp:489] Master detector found 1
> registered masters
> 2013-05-29 14:28:54,952:9122(0x7fdedc96f700):ZOO_DEBUG@zoo_awget@2414:
> Sending request xid=0x51a648e9 for path [/mesos/0000000000] to
> 192.168.7.249:2181
> 2013-05-29 14:28:54,954:9122(0x7fded9700700):ZOO_DEBUG@zookeeper_process@1989:
> Queueing asynchronous response
> 2013-05-29 14:28:54,954:9122(0x7fded8cff700):ZOO_DEBUG@process_completions@1772:
> Calling COMPLETION_DATA for xid=0x51a648e9 rc=0
> I0529 14:28:54.954154  9136 detector.cpp:535] Master detector got new
> master pid: master@127.0.0.1:5050
> I0529 14:28:54.954272  9136 slave.cpp:352] New master detected at
> master@127.0.0.1:5050
> I0529 14:28:54.954807  9136 slave.cpp:1141] Process exited: @0.0.0.0:0
> W0529 14:28:54.954829  9136 slave.cpp:1144] WARNING! Master disconnected!
> Waiting for a new master to be elected.
>
> This is at startup. There is nothing running on port 5050 on the server
> for it to detect.
>
> From: Benjamin Hindman <benh@eecs.berkeley.edu<mailto:
> benh@eecs.berkeley.edu>>
> Date: Wednesday, May 29, 2013 1:52 PM
> To: mesos <mesos-dev@incubator.apache.org<mailto:
> mesos-dev@incubator.apache.org>>
> Cc: Julien <Ju...@Vimeo.com>>
> Subject: Re: user seeking help on #mesos
>
>
> Also, support for config files is being deprecated (from 0.13.0). So, I
> would suggest to not rely on them.
>
> You'll still be able to use something like a config file though, you can
> set flags via environment variables (e.g., MESOS_master=...) and you can
> put all of your environment variables in a single file that you 'source'
> before launching one of the binaries (or, my preference, just have a script
> that launches the binary directly "configuring" it but via the command line
> ... an "active config file" if you will).
>
>
>
>
>
> On Wed, May 29, 2013 at 10:17 AM, Eid, Julien <Julien@vimeo.com<mailto:
> Julien@vimeo.com>> wrote:
>
> >  Thanks for getting back to me! I'm using mesos-0.10.0. I'm talking about
> > on the masters I currently specify the location for zookeeper servers
> like
> > this --zk=zk://mesos1:2181,mesos2:2181,mesos3:2181/mesos
> >
> >  And for slaves I specify the masters like this
> > --master=zk://mesos1:2181,mesos2:2181,mesos3:2181/mesos
> >
> >  I want to specify these in config files so I can start them without
> > having to specify that on the command line.
> >
> >   From: Vinod Kone <vi...@gmail.com>>
> > Date: Wednesday, May 29, 2013 1:13 PM
> > To: "mesos-dev@incubator.apache.org<mailto:
> mesos-dev@incubator.apache.org>" <mesos-dev@incubator.apache.org<mailto:
> mesos-dev@incubator.apache.org>>
> > Cc: Julien <Ju...@Vimeo.com>>
> > Subject: Re: user seeking help on #mesos
> >
> >   Hey Julien,
> >
> >  What version of mesos are you running?
> >
> >  What do you mean by "specify the zookeeper option somewhere"? Do you
> > mean the slave?
> >
> >
> > On Wed, May 29, 2013 at 9:53 AM, Adam Monsen <haircut@gmail.com<mailto:
> haircut@gmail.com>> wrote:
> >
> >> Someone (Cc'd) is asking for help in #mesos (on Freenode). Is anyone
> >> available to stop by and answer a couple of questions?
> >>
> >> > [09:48] < jeid> I just had some questions about config files.
> >> > [09:48] < jeid> I think the github docs are out of date.
> >> > [09:48] < jeid> And aren't really helpful.
> >> > [09:49] < jeid> I have hot-master and all my slaves working with
> >> > zookeeper
> >> > [09:49] < jeid> however I start all of my services by hand
> >> > [09:49] < jeid> doing ./mesos-master
> >> > --zk=zk://zookeeper1:2181,zk2:2181/mesos
> >> > [09:49] < jeid> I want to specify that zookeeper option somewhere
> >> > but the docs don't specify it anywhere.
> >> > [09:49] < jeid> so I just want to do ./mesos-daemon
> >> > [09:50] < jeid> in the future.
> >>
> >
> >
>
>

Re: user seeking help on #mesos

Posted by "Eid, Julien" <Ju...@Vimeo.com>.
Okay, I'll use the active config way to configure it. I also seem to get this weird bug where my slaves can't connect to the masters. It appears to detect a master running on localhost even though there is none, then disconnects, and is unable to find any other masters using zookeeper.

2013-05-29 14:28:54,952:9122(0x7fded8cff700):ZOO_DEBUG@process_completions@1795: Calling COMPLETION_STRINGLIST for xid=0x51a648e8 rc=0
I0529 14:28:54.952693  9136 detector.cpp:489] Master detector found 1 registered masters
2013-05-29 14:28:54,952:9122(0x7fdedc96f700):ZOO_DEBUG@zoo_awget@2414: Sending request xid=0x51a648e9 for path [/mesos/0000000000] to 192.168.7.249:2181
2013-05-29 14:28:54,954:9122(0x7fded9700700):ZOO_DEBUG@zookeeper_process@1989: Queueing asynchronous response
2013-05-29 14:28:54,954:9122(0x7fded8cff700):ZOO_DEBUG@process_completions@1772: Calling COMPLETION_DATA for xid=0x51a648e9 rc=0
I0529 14:28:54.954154  9136 detector.cpp:535] Master detector got new master pid: master@127.0.0.1:5050
I0529 14:28:54.954272  9136 slave.cpp:352] New master detected at master@127.0.0.1:5050
I0529 14:28:54.954807  9136 slave.cpp:1141] Process exited: @0.0.0.0:0
W0529 14:28:54.954829  9136 slave.cpp:1144] WARNING! Master disconnected! Waiting for a new master to be elected.

This is at startup. There is nothing running on port 5050 on the server for it to detect.

From: Benjamin Hindman <be...@eecs.berkeley.edu>>
Date: Wednesday, May 29, 2013 1:52 PM
To: mesos <me...@incubator.apache.org>>
Cc: Julien <Ju...@Vimeo.com>>
Subject: Re: user seeking help on #mesos


Also, support for config files is being deprecated (from 0.13.0). So, I
would suggest to not rely on them.

You'll still be able to use something like a config file though, you can set flags via environment variables (e.g., MESOS_master=...) and you can put all of your environment variables in a single file that you 'source' before launching one of the binaries (or, my preference, just have a script that launches the binary directly "configuring" it but via the command line ... an "active config file" if you will).





On Wed, May 29, 2013 at 10:17 AM, Eid, Julien <Ju...@vimeo.com>> wrote:

>  Thanks for getting back to me! I'm using mesos-0.10.0. I'm talking about
> on the masters I currently specify the location for zookeeper servers like
> this --zk=zk://mesos1:2181,mesos2:2181,mesos3:2181/mesos
>
>  And for slaves I specify the masters like this
> --master=zk://mesos1:2181,mesos2:2181,mesos3:2181/mesos
>
>  I want to specify these in config files so I can start them without
> having to specify that on the command line.
>
>   From: Vinod Kone <vi...@gmail.com>>
> Date: Wednesday, May 29, 2013 1:13 PM
> To: "mesos-dev@incubator.apache.org<ma...@incubator.apache.org>" <me...@incubator.apache.org>>
> Cc: Julien <Ju...@Vimeo.com>>
> Subject: Re: user seeking help on #mesos
>
>   Hey Julien,
>
>  What version of mesos are you running?
>
>  What do you mean by "specify the zookeeper option somewhere"? Do you
> mean the slave?
>
>
> On Wed, May 29, 2013 at 9:53 AM, Adam Monsen <ha...@gmail.com>> wrote:
>
>> Someone (Cc'd) is asking for help in #mesos (on Freenode). Is anyone
>> available to stop by and answer a couple of questions?
>>
>> > [09:48] < jeid> I just had some questions about config files.
>> > [09:48] < jeid> I think the github docs are out of date.
>> > [09:48] < jeid> And aren't really helpful.
>> > [09:49] < jeid> I have hot-master and all my slaves working with
>> > zookeeper
>> > [09:49] < jeid> however I start all of my services by hand
>> > [09:49] < jeid> doing ./mesos-master
>> > --zk=zk://zookeeper1:2181,zk2:2181/mesos
>> > [09:49] < jeid> I want to specify that zookeeper option somewhere
>> > but the docs don't specify it anywhere.
>> > [09:49] < jeid> so I just want to do ./mesos-daemon
>> > [09:50] < jeid> in the future.
>>
>
>


Re: user seeking help on #mesos

Posted by Benjamin Hindman <be...@eecs.berkeley.edu>.
> Also, support for config files is being deprecated (from 0.13.0). So, I
> would suggest to not rely on them.
>

You'll still be able to use something like a config file though, you can
set flags via environment variables (e.g., MESOS_master=...) and you can
put all of your environment variables in a single file that you 'source'
before launching one of the binaries (or, my preference, just have a script
that launches the binary directly "configuring" it but via the command line
... an "active config file" if you will).




>
>
> On Wed, May 29, 2013 at 10:17 AM, Eid, Julien <Ju...@vimeo.com> wrote:
>
> >  Thanks for getting back to me! I'm using mesos-0.10.0. I'm talking about
> > on the masters I currently specify the location for zookeeper servers
> like
> > this --zk=zk://mesos1:2181,mesos2:2181,mesos3:2181/mesos
> >
> >  And for slaves I specify the masters like this
> > --master=zk://mesos1:2181,mesos2:2181,mesos3:2181/mesos
> >
> >  I want to specify these in config files so I can start them without
> > having to specify that on the command line.
> >
> >   From: Vinod Kone <vi...@gmail.com>
> > Date: Wednesday, May 29, 2013 1:13 PM
> > To: "mesos-dev@incubator.apache.org" <me...@incubator.apache.org>
> > Cc: Julien <Ju...@Vimeo.com>
> > Subject: Re: user seeking help on #mesos
> >
> >   Hey Julien,
> >
> >  What version of mesos are you running?
> >
> >  What do you mean by "specify the zookeeper option somewhere"? Do you
> > mean the slave?
> >
> >
> > On Wed, May 29, 2013 at 9:53 AM, Adam Monsen <ha...@gmail.com> wrote:
> >
> >> Someone (Cc'd) is asking for help in #mesos (on Freenode). Is anyone
> >> available to stop by and answer a couple of questions?
> >>
> >> > [09:48] < jeid> I just had some questions about config files.
> >> > [09:48] < jeid> I think the github docs are out of date.
> >> > [09:48] < jeid> And aren't really helpful.
> >> > [09:49] < jeid> I have hot-master and all my slaves working with
> >> > zookeeper
> >> > [09:49] < jeid> however I start all of my services by hand
> >> > [09:49] < jeid> doing ./mesos-master
> >> > --zk=zk://zookeeper1:2181,zk2:2181/mesos
> >> > [09:49] < jeid> I want to specify that zookeeper option somewhere
> >> > but the docs don't specify it anywhere.
> >> > [09:49] < jeid> so I just want to do ./mesos-daemon
> >> > [09:50] < jeid> in the future.
> >>
> >
> >
>

Re: user seeking help on #mesos

Posted by Vinod Kone <vi...@gmail.com>.
Do  "zk=..." and "master=..." in config file(s) not work ?

Also, support for config files is being deprecated (from 0.13.0). So, I
would suggest to not rely on them.


On Wed, May 29, 2013 at 10:17 AM, Eid, Julien <Ju...@vimeo.com> wrote:

>  Thanks for getting back to me! I'm using mesos-0.10.0. I'm talking about
> on the masters I currently specify the location for zookeeper servers like
> this --zk=zk://mesos1:2181,mesos2:2181,mesos3:2181/mesos
>
>  And for slaves I specify the masters like this
> --master=zk://mesos1:2181,mesos2:2181,mesos3:2181/mesos
>
>  I want to specify these in config files so I can start them without
> having to specify that on the command line.
>
>   From: Vinod Kone <vi...@gmail.com>
> Date: Wednesday, May 29, 2013 1:13 PM
> To: "mesos-dev@incubator.apache.org" <me...@incubator.apache.org>
> Cc: Julien <Ju...@Vimeo.com>
> Subject: Re: user seeking help on #mesos
>
>   Hey Julien,
>
>  What version of mesos are you running?
>
>  What do you mean by "specify the zookeeper option somewhere"? Do you
> mean the slave?
>
>
> On Wed, May 29, 2013 at 9:53 AM, Adam Monsen <ha...@gmail.com> wrote:
>
>> Someone (Cc'd) is asking for help in #mesos (on Freenode). Is anyone
>> available to stop by and answer a couple of questions?
>>
>> > [09:48] < jeid> I just had some questions about config files.
>> > [09:48] < jeid> I think the github docs are out of date.
>> > [09:48] < jeid> And aren't really helpful.
>> > [09:49] < jeid> I have hot-master and all my slaves working with
>> > zookeeper
>> > [09:49] < jeid> however I start all of my services by hand
>> > [09:49] < jeid> doing ./mesos-master
>> > --zk=zk://zookeeper1:2181,zk2:2181/mesos
>> > [09:49] < jeid> I want to specify that zookeeper option somewhere
>> > but the docs don't specify it anywhere.
>> > [09:49] < jeid> so I just want to do ./mesos-daemon
>> > [09:50] < jeid> in the future.
>>
>
>

Re: user seeking help on #mesos

Posted by "Eid, Julien" <Ju...@Vimeo.com>.
Thanks for getting back to me! I'm using mesos-0.10.0. I'm talking about on the masters I currently specify the location for zookeeper servers like this --zk=zk://mesos1:2181,mesos2:2181,mesos3:2181/mesos

And for slaves I specify the masters like this
--master=zk://mesos1:2181,mesos2:2181,mesos3:2181/mesos

I want to specify these in config files so I can start them without having to specify that on the command line.

From: Vinod Kone <vi...@gmail.com>>
Date: Wednesday, May 29, 2013 1:13 PM
To: "mesos-dev@incubator.apache.org<ma...@incubator.apache.org>" <me...@incubator.apache.org>>
Cc: Julien <Ju...@Vimeo.com>>
Subject: Re: user seeking help on #mesos

Hey Julien,

What version of mesos are you running?

What do you mean by "specify the zookeeper option somewhere"? Do you mean the slave?


On Wed, May 29, 2013 at 9:53 AM, Adam Monsen <ha...@gmail.com>> wrote:
Someone (Cc'd) is asking for help in #mesos (on Freenode). Is anyone
available to stop by and answer a couple of questions?

> [09:48] < jeid> I just had some questions about config files.
> [09:48] < jeid> I think the github docs are out of date.
> [09:48] < jeid> And aren't really helpful.
> [09:49] < jeid> I have hot-master and all my slaves working with
> zookeeper
> [09:49] < jeid> however I start all of my services by hand
> [09:49] < jeid> doing ./mesos-master
> --zk=zk://zookeeper1:2181,zk2:2181/mesos
> [09:49] < jeid> I want to specify that zookeeper option somewhere
> but the docs don't specify it anywhere.
> [09:49] < jeid> so I just want to do ./mesos-daemon
> [09:50] < jeid> in the future.


Re: user seeking help on #mesos

Posted by Vinod Kone <vi...@gmail.com>.
Hey Julien,

What version of mesos are you running?

What do you mean by "specify the zookeeper option somewhere"? Do you mean
the slave?


On Wed, May 29, 2013 at 9:53 AM, Adam Monsen <ha...@gmail.com> wrote:

> Someone (Cc'd) is asking for help in #mesos (on Freenode). Is anyone
> available to stop by and answer a couple of questions?
>
> > [09:48] < jeid> I just had some questions about config files.
> > [09:48] < jeid> I think the github docs are out of date.
> > [09:48] < jeid> And aren't really helpful.
> > [09:49] < jeid> I have hot-master and all my slaves working with
> > zookeeper
> > [09:49] < jeid> however I start all of my services by hand
> > [09:49] < jeid> doing ./mesos-master
> > --zk=zk://zookeeper1:2181,zk2:2181/mesos
> > [09:49] < jeid> I want to specify that zookeeper option somewhere
> > but the docs don't specify it anywhere.
> > [09:49] < jeid> so I just want to do ./mesos-daemon
> > [09:50] < jeid> in the future.
>