Not sure what you mean by determine. So I'll just blabber about how I debugged. During marathon's startup the ZK library emits some messages that say what it's connecting to and where it's registering. In my case the string looked like ,hostname/mesos instead of "mesos". I poked at it with zkCLI (or whatever the name is) and saw it was wrong.
Also, my hosts were registering with the hostname "localhost" so they all thought they were masters. :P Anyway, I hope that helps some. On Thu, Apr 10, 2014 at 9:09 AM, David J. Palaitis < [email protected]> wrote: > Thanks. I tried that but still not seeing marathon in the list of active > frameworks. > > naive question, how can I determine the zk master string? > > > On Thu, Apr 10, 2014 at 11:35 AM, Cory Watson <[email protected]> wrote: > >> Hey David, >> >> This might or might not be a factor, but you should only have /mesos on >> the very end of your zk master string. so zk://host1:2181,host2:2181/mesos >> >> I had a lot of trouble with that as well and sent some updated docs with >> were rolled in. Could you try that and see if it helps? >> >> >> On Thu, Apr 10, 2014 at 8:33 AM, David J. Palaitis < >> [email protected]> wrote: >> >>> starting marathon ... >>> >>> ./bin/start --http_port 5150 --https_port 5151 --master >>> "zk://abc.xxx:2181/mesos,def.xxx:2181/mesos,ghi.xxx:2181/mesos,ghi.xxx:2181/mesos,hij.xxx:2181/mesos" >>> --zkhosts abc.xxx.pit:2181 >>> >>> I see a zk connection established: >>> >>> 2014-04-10 15:30:07,047:38588(0x7fded64f0910):ZOO_INFO@check_events@1750: >>> session establishment complete on server [WWW.XXX.YYY.ZZZ.:2181], >>> sessionId=0x244c63e923d0002, negotiated timeout=10000 >>> >>> but the framework is not listed. >>> >>> >>> >> >> >> -- >> Cory Watson >> Principal Infrastructure Engineer // Keen IO >> > > -- Cory Watson Principal Infrastructure Engineer // Keen IO
