Re: [VOTE] Release Apache Mesos 0.24.0 (rc2)

[Alex Rukletsov]

Afaik, Pythontest is flaky on OS X, and should be fine on Ubuntu.
On 4 Sep 2015 10:48 pm, "Bernd Mathiske"  wrote:

> And also Ubuntu 13.10: [  FAILED  ] ExamplesTest.PythonFramework, known
> flaky test, so still +1
>
> On Sep 4, 2015, at 9:11 PM, Bernd Mathiske  wrote:
>
> +1 [binding]
>
> MacOS X (make check)
> CentOS 7 (make distcheck)
> Ubuntu 14.4 (make distcheck)
>
>
> On Sep 3, 2015, at 11:47 PM, Niklas Nielsen  wrote:
>
> +1 - tested on our CI
>
> On Tuesday, September 1, 2015, Vinod Kone  wrote:
>
>> Hi all,
>>
>>
>> Please vote on releasing the following candidate as Apache Mesos 0.24.0.
>>
>>
>> 0.24.0 includes the following:
>>
>>
>> 
>>
>> Experimental support for v1 scheduler HTTP API!
>>
>> This release also wraps up support for fetcher.
>>
>> The CHANGELOG for the release is available at:
>>
>>
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.24.0-rc2
>>
>>
>> 
>>
>>
>> The candidate for Mesos 0.24.0 release is available at:
>>
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.24.0-rc2/mesos-0.24.0.tar.gz
>>
>>
>> The tag to be voted on is 0.24.0-rc2:
>>
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.24.0-rc2
>>
>>
>> The MD5 checksum of the tarball can be found at:
>>
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.24.0-rc2/mesos-0.24.0.tar.gz.md5
>>
>>
>> The signature of the tarball can be found at:
>>
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.24.0-rc2/mesos-0.24.0.tar.gz.asc
>>
>>
>> The PGP key used to sign the release is here:
>>
>> https://dist.apache.org/repos/dist/release/mesos/KEYS
>>
>>
>> The JAR is up in Maven in a staging repository here:
>>
>> https://repository.apache.org/content/repositories/orgapachemesos-1066
>>
>>
>> Please vote on releasing this package as Apache Mesos 0.24.0!
>>
>>
>> The vote is open until Fri Sep  4 17:33:05 PDT 2015 and passes if a
>> majority of at least 3 +1 PMC votes are cast.
>>
>>
>> [ ] +1 Release this package as Apache Mesos 0.24.0
>>
>> [ ] -1 Do not release this package because ...
>>
>>
>> Thanks,
>>
>> Vinod
>>
>
>
>

RE: Basic installation question

[Klaus Ma]

Can you share the command line of master & slave? According the following 
information, it seems master run without "--zk" option.



Regards,Klaus Ma (马达), PMP® | http://www.cguru.net
CallSend SMSCall from mobileAdd to SkypeYou'll need Skype CreditFree via 
SkypeCallSend SMSCall from mobileAdd to SkypeYou'll need Skype CreditFree via 
SkypeDate: Fri, 4 Sep 2015 17:33:45 -0700
Subject: Re: Basic installation question
From: java...@gmail.com
To: user@mesos.apache.org


I installed using yum -y install mesos. That did work.   
Now the master and slaves do not see each other.

Here is the master:
$ ps -ef | grep mesos | grep -v grepstack30236 17902  0 00:09 pts/4
00:00:04 /mnt/mesos/build/src/.libs/lt-mesos-master --work_dir=/tmp/mesos 
--ip=10.xx.xx.124

Here is one of the 20 slaves:
 ps -ef | grep mesos | grep -v greproot 26086 1  0 00:10 ?
00:00:00 /usr/sbin/mesos-slave --master=zk://10.xx.xx.124:2181/mesos 
--log_dir=/var/log/mesosroot 26092 26086  0 00:10 ?00:00:00 logger 
-p user.info -t mesos-slave[26086]root 26093 26086  0 00:10 ?
00:00:00 logger -p user.err -t mesos-slave[26086]

Note the slave and master are on correct same ip address
The /etc/mesos/zk seems to be set properly : and I do see the /mesos node in 
zookeeper is updated after restarting the master
However the zookeeper node is empty:
[zk: localhost:2181(CONNECTED) 10] ls /mesos[]
The node is world accessible so no permission issue:
[zk: localhost:2181(CONNECTED) 12] getAcl /mesos
'world,'anyone: cdrwa
Why is the zookeeper node empty?  Is this the reason the  master and slaves are 
not connecting?
2015-09-04 14:56 GMT-07:00 craig w :
No problem, they have a "downloads" link inn their menu: 
https://mesosphere.com/downloads/
On Sep 4, 2015 5:43 PM, "Stephen Boesch"  wrote:
@Craig . That is an incomplete answer - given that such links are not presented 
in an obvious manner .  Maybe you managed to find  a link on their site that 
provides prebuilt for Centos7: if so then please share it.   
I had previously found a link on their site for prebuilt binaries but is based 
on using CDH4 (which is not possible for my company). It is also old. 
https://docs.mesosphere.com/tutorials/install_centos_rhel/


2015-09-04 14:27 GMT-07:00 craig w :
Mesosphere has packages prebuilt, go to their site to find how to install
On Sep 4, 2015 5:11 PM, "Stephen Boesch"  wrote:

After following the directions here:   http://mesos.apache.org/gettingstarted/
Which for centos7 includes the following:



  # Change working directory.
$ cd mesos

# Bootstrap (Only required if building from git repository).
$ ./bootstrap

# Configure and build.
$ mkdir build
$ cd build
$ ../configure
$ make
In order to speed up the build and reduce verbosity of the logs, you can 
append-j  V=0 to make.# Run test suite.
$ make check

# Install (Optional).
$ make install

But the installation is not correct afterwards: here is the bin directory:
$ ll bintotal 92-rw-r--r--.  1 stack stack 1769 Jul 17 23:14 
valgrind-mesos-tests.sh.in-rw-r--r--.  1 stack stack 1769 Jul 17 23:14 
valgrind-mesos-slave.sh.in-rw-r--r--.  1 stack stack 1772 Jul 17 23:14 
valgrind-mesos-master.sh.in-rw-r--r--.  1 stack stack 1769 Jul 17 23:14 
valgrind-mesos-local.sh.in-rw-r--r--.  1 stack stack 1026 Jul 17 23:14 
mesos-tests.sh.in-rw-r--r--.  1 stack stack  901 Jul 17 23:14 
mesos-tests-flags.sh.in-rw-r--r--.  1 stack stack 1019 Jul 17 23:14 
mesos-slave.sh.in-rw-r--r--.  1 stack stack 1721 Jul 17 23:14 
mesos-slave-flags.sh.in-rw-r--r--.  1 stack stack 1366 Jul 17 23:14 
mesos.sh.in-rw-r--r--.  1 stack stack 1026 Jul 17 23:14 
mesos-master.sh.in-rw-r--r--.  1 stack stack  858 Jul 17 23:14 
mesos-master-flags.sh.in-rw-r--r--.  1 stack stack 1023 Jul 17 23:14 
mesos-local.sh.in-rw-r--r--.  1 stack stack  935 Jul 17 23:14 
mesos-local-flags.sh.in-rw-r--r--.  1 stack stack 1466 Jul 17 23:14 
lldb-mesos-tests.sh.in-rw-r--r--.  1 stack stack 1489 Jul 17 23:14 
lldb-mesos-slave.sh.in-rw-r--r--.  1 stack stack 1492 Jul 17 23:14 
lldb-mesos-master.sh.in-rw-r--r--.  1 stack stack 1489 Jul 17 23:14 
lldb-mesos-local.sh.in-rw-r--r--.  1 stack stack 1498 Jul 17 23:14 
gdb-mesos-tests.sh.in-rw-r--r--.  1 stack stack 1527 Jul 17 23:14 
gdb-mesos-slave.sh.in-rw-r--r--.  1 stack stack 1530 Jul 17 23:14 
gdb-mesos-master.sh.in-rw-r--r--.  1 stack stack 1521 Jul 17 23:14 
gdb-mesos-local.sh.indrwxr-xr-x.  2 stack stack 4096 Jul 17 23:21 .drwxr-xr-x. 
11 stack stack 4096 Sep  4 20:08 ..
So .. two things:
(a) what is missing from the installation instructions?
(b) Is there an up to date rpm/yum installation for centos7?











  

Re: Basic installation question

[Marco Massenzio]

Stephen:

Klaus is correct, you are starting the Master in "standalone" mode, not
with zookeeper support: it needs adding the --zk=zk://10.xx.xx.124:2181/mesos
--quorum=1 options (at the very least).

As you correctly noted, the contents of the /mesos znode is empty and thus
the agent nodes cannot find elected Master leader (also, if you are running
more than one Master, they won't 'know' about each other and won't be able
to elect a leader).

To check that your settings work, you can (a) look in Master logs (it will
log a lot of info when connecting to ZK) and (b) see that under /mesos a
number of json.info_nn nodes will appear (whose contents are JSON so
you can double check that the contents make sense).

You can find more info here[0].

[0]
http://codetrips.com/2015/08/16/apache-mesos-leader-master-discovery-using-zookeeper-part-2/

*Marco Massenzio*

*Distributed Systems Engineerhttp://codetrips.com *

On Fri, Sep 4, 2015 at 5:33 PM, Stephen Boesch  wrote:

>
> I installed using yum -y install mesos. That did work.
>
> Now the master and slaves do not see each other.
>
>
> Here is the master:
> $ ps -ef | grep mesos | grep -v grep
> stack30236 17902  0 00:09 pts/400:00:04
> /mnt/mesos/build/src/.libs/lt-mesos-master --work_dir=/tmp/mesos
> --ip=10.xx.xx.124
>
>
> Here is one of the 20 slaves:
>
>  ps -ef | grep mesos | grep -v grep
> root 26086 1  0 00:10 ?00:00:00 /usr/sbin/mesos-slave
> --master=zk://10.xx.xx.124:2181/mesos --log_dir=/var/log/mesos
> root 26092 26086  0 00:10 ?00:00:00 logger -p user.info -t
> mesos-slave[26086]
> root 26093 26086  0 00:10 ?00:00:00 logger -p user.err -t
> mesos-slave[26086]
>
>
> Note the slave and master are on correct same ip address
>
> The /etc/mesos/zk seems to be set properly : and I do see the /mesos node
> in zookeeper is updated after restarting the master
>
> However the zookeeper node is empty:
>
> [zk: localhost:2181(CONNECTED) 10] ls /mesos
> []
>
> The node is world accessible so no permission issue:
>
> [zk: localhost:2181(CONNECTED) 12] getAcl /mesos
> 'world,'anyone
> : cdrwa
>
> Why is the zookeeper node empty?  Is this the reason the  master and
> slaves are not connecting?
>
> 2015-09-04 14:56 GMT-07:00 craig w :
>
>> No problem, they have a "downloads" link inn their menu:
>> https://mesosphere.com/downloads/
>> On Sep 4, 2015 5:43 PM, "Stephen Boesch"  wrote:
>>
>>> @Craig . That is an incomplete answer - given that such links are not
>>> presented in an obvious manner .  Maybe you managed to find  a link on
>>> their site that provides prebuilt for Centos7: if so then please share it.
>>>
>>>
>>> I had previously found a link on their site for prebuilt binaries but is
>>> based on using CDH4 (which is not possible for my company). It is also old.
>>>
>>> https://docs.mesosphere.com/tutorials/install_centos_rhel/
>>>
>>>
>>> 2015-09-04 14:27 GMT-07:00 craig w :
>>>
 Mesosphere has packages prebuilt, go to their site to find how to
 install
 On Sep 4, 2015 5:11 PM, "Stephen Boesch"  wrote:

>
> After following the directions here:
> http://mesos.apache.org/gettingstarted/
>
> Which for centos7 includes the following:
>
>
>
>
>   # Change working directory.
> $ cd mesos
>
> # Bootstrap (Only required if building from git repository).
> $ ./bootstrap
>
> # Configure and build.
> $ mkdir build
> $ cd build
> $ ../configure
> $ make
>
> In order to speed up the build and reduce verbosity of the logs, you
> can append-j  V=0 to make.
>
> # Run test suite.
> $ make check
>
> # Install (Optional).
> $ make install
>
>
>
> But the installation is not correct afterwards: here is the bin
> directory:
>
> $ ll bin
> total 92
> -rw-r--r--.  1 stack stack 1769 Jul 17 23:14
> valgrind-mesos-tests.sh.in
> -rw-r--r--.  1 stack stack 1769 Jul 17 23:14
> valgrind-mesos-slave.sh.in
> -rw-r--r--.  1 stack stack 1772 Jul 17 23:14
> valgrind-mesos-master.sh.in
> -rw-r--r--.  1 stack stack 1769 Jul 17 23:14
> valgrind-mesos-local.sh.in
> -rw-r--r--.  1 stack stack 1026 Jul 17 23:14 mesos-tests.sh.in
> -rw-r--r--.  1 stack stack  901 Jul 17 23:14 mesos-tests-flags.sh.in
> -rw-r--r--.  1 stack stack 1019 Jul 17 23:14 mesos-slave.sh.in
> -rw-r--r--.  1 stack stack 1721 Jul 17 23:14 mesos-slave-flags.sh.in
> -rw-r--r--.  1 stack stack 1366 Jul 17 23:14 mesos.sh.in
> -rw-r--r--.  1 stack stack 1026 Jul 17 23:14 mesos-master.sh.in
> -rw-r--r--.  1 stack stack  858 Jul 17 23:14 mesos-master-flags.sh.in
> -rw-r--r--.  1 stack stack 1023 Jul 17 23:14 mesos-local.sh.in
> -rw-r--r--.  1 stack stack  935 Jul 17 23:14 

Re: Basic installation question

[Marco Massenzio]

Thanks for follow-up, Stephen - this will be also useful to others finding
this in the archives!

Glad it eventually worked for you, I'll drop a line to our guys to update
the download page with this information, so it should hopefully be less
painful in the future for others.

*Marco Massenzio*

*Distributed Systems Engineerhttp://codetrips.com *

On Sat, Sep 5, 2015 at 3:00 PM, Stephen Boesch  wrote:

> Yes I had started the slaves as
>
> service mesos-slave start
>
> But had not done the correct way on the master, which is supposed to be:
>
> service mesos-master start
>
> The slaves do appear after having made that correction: thanks.
>
>
> 2015-09-05 14:55 GMT-07:00 Marco Massenzio :
>
>> Stephen:
>>
>> Klaus is correct, you are starting the Master in "standalone" mode, not
>> with zookeeper support: it needs adding the --zk=zk://10.xx.xx.124:2181/mesos
>> --quorum=1 options (at the very least).
>>
>> As you correctly noted, the contents of the /mesos znode is empty and
>> thus the agent nodes cannot find elected Master leader (also, if you are
>> running more than one Master, they won't 'know' about each other and won't
>> be able to elect a leader).
>>
>> To check that your settings work, you can (a) look in Master logs (it
>> will log a lot of info when connecting to ZK) and (b) see that under /mesos
>> a number of json.info_nn nodes will appear (whose contents are JSON so
>> you can double check that the contents make sense).
>>
>> You can find more info here[0].
>>
>> [0]
>> http://codetrips.com/2015/08/16/apache-mesos-leader-master-discovery-using-zookeeper-part-2/
>>
>> *Marco Massenzio*
>>
>> *Distributed Systems Engineerhttp://codetrips.com *
>>
>> On Fri, Sep 4, 2015 at 5:33 PM, Stephen Boesch  wrote:
>>
>>>
>>> I installed using yum -y install mesos. That did work.
>>>
>>> Now the master and slaves do not see each other.
>>>
>>>
>>> Here is the master:
>>> $ ps -ef | grep mesos | grep -v grep
>>> stack30236 17902  0 00:09 pts/400:00:04
>>> /mnt/mesos/build/src/.libs/lt-mesos-master --work_dir=/tmp/mesos
>>> --ip=10.xx.xx.124
>>>
>>>
>>> Here is one of the 20 slaves:
>>>
>>>  ps -ef | grep mesos | grep -v grep
>>> root 26086 1  0 00:10 ?00:00:00 /usr/sbin/mesos-slave
>>> --master=zk://10.xx.xx.124:2181/mesos --log_dir=/var/log/mesos
>>> root 26092 26086  0 00:10 ?00:00:00 logger -p user.info -t
>>> mesos-slave[26086]
>>> root 26093 26086  0 00:10 ?00:00:00 logger -p user.err -t
>>> mesos-slave[26086]
>>>
>>>
>>> Note the slave and master are on correct same ip address
>>>
>>> The /etc/mesos/zk seems to be set properly : and I do see the /mesos
>>> node in zookeeper is updated after restarting the master
>>>
>>> However the zookeeper node is empty:
>>>
>>> [zk: localhost:2181(CONNECTED) 10] ls /mesos
>>> []
>>>
>>> The node is world accessible so no permission issue:
>>>
>>> [zk: localhost:2181(CONNECTED) 12] getAcl /mesos
>>> 'world,'anyone
>>> : cdrwa
>>>
>>> Why is the zookeeper node empty?  Is this the reason the  master and
>>> slaves are not connecting?
>>>
>>> 2015-09-04 14:56 GMT-07:00 craig w :
>>>
 No problem, they have a "downloads" link inn their menu:
 https://mesosphere.com/downloads/
 On Sep 4, 2015 5:43 PM, "Stephen Boesch"  wrote:

> @Craig . That is an incomplete answer - given that such links are not
> presented in an obvious manner .  Maybe you managed to find  a link on
> their site that provides prebuilt for Centos7: if so then please share it.
>
>
> I had previously found a link on their site for prebuilt binaries but
> is based on using CDH4 (which is not possible for my company). It is also
> old.
>
> https://docs.mesosphere.com/tutorials/install_centos_rhel/
>
>
> 2015-09-04 14:27 GMT-07:00 craig w :
>
>> Mesosphere has packages prebuilt, go to their site to find how to
>> install
>> On Sep 4, 2015 5:11 PM, "Stephen Boesch"  wrote:
>>
>>>
>>> After following the directions here:
>>> http://mesos.apache.org/gettingstarted/
>>>
>>> Which for centos7 includes the following:
>>>
>>>
>>>
>>>
>>>   # Change working directory.
>>> $ cd mesos
>>>
>>> # Bootstrap (Only required if building from git repository).
>>> $ ./bootstrap
>>>
>>> # Configure and build.
>>> $ mkdir build
>>> $ cd build
>>> $ ../configure
>>> $ make
>>>
>>> In order to speed up the build and reduce verbosity of the logs, you
>>> can append-j  V=0 to make.
>>>
>>> # Run test suite.
>>> $ make check
>>>
>>> # Install (Optional).
>>> $ make install
>>>
>>>
>>>
>>> But the installation is not correct 

Re: Basic installation question

[Stephen Boesch]

Yes I had started the slaves as

service mesos-slave start

But had not done the correct way on the master, which is supposed to be:

service mesos-master start

The slaves do appear after having made that correction: thanks.


2015-09-05 14:55 GMT-07:00 Marco Massenzio :

> Stephen:
>
> Klaus is correct, you are starting the Master in "standalone" mode, not
> with zookeeper support: it needs adding the --zk=zk://10.xx.xx.124:2181/mesos
> --quorum=1 options (at the very least).
>
> As you correctly noted, the contents of the /mesos znode is empty and thus
> the agent nodes cannot find elected Master leader (also, if you are running
> more than one Master, they won't 'know' about each other and won't be able
> to elect a leader).
>
> To check that your settings work, you can (a) look in Master logs (it will
> log a lot of info when connecting to ZK) and (b) see that under /mesos a
> number of json.info_nn nodes will appear (whose contents are JSON so
> you can double check that the contents make sense).
>
> You can find more info here[0].
>
> [0]
> http://codetrips.com/2015/08/16/apache-mesos-leader-master-discovery-using-zookeeper-part-2/
>
> *Marco Massenzio*
>
> *Distributed Systems Engineerhttp://codetrips.com *
>
> On Fri, Sep 4, 2015 at 5:33 PM, Stephen Boesch  wrote:
>
>>
>> I installed using yum -y install mesos. That did work.
>>
>> Now the master and slaves do not see each other.
>>
>>
>> Here is the master:
>> $ ps -ef | grep mesos | grep -v grep
>> stack30236 17902  0 00:09 pts/400:00:04
>> /mnt/mesos/build/src/.libs/lt-mesos-master --work_dir=/tmp/mesos
>> --ip=10.xx.xx.124
>>
>>
>> Here is one of the 20 slaves:
>>
>>  ps -ef | grep mesos | grep -v grep
>> root 26086 1  0 00:10 ?00:00:00 /usr/sbin/mesos-slave
>> --master=zk://10.xx.xx.124:2181/mesos --log_dir=/var/log/mesos
>> root 26092 26086  0 00:10 ?00:00:00 logger -p user.info -t
>> mesos-slave[26086]
>> root 26093 26086  0 00:10 ?00:00:00 logger -p user.err -t
>> mesos-slave[26086]
>>
>>
>> Note the slave and master are on correct same ip address
>>
>> The /etc/mesos/zk seems to be set properly : and I do see the /mesos node
>> in zookeeper is updated after restarting the master
>>
>> However the zookeeper node is empty:
>>
>> [zk: localhost:2181(CONNECTED) 10] ls /mesos
>> []
>>
>> The node is world accessible so no permission issue:
>>
>> [zk: localhost:2181(CONNECTED) 12] getAcl /mesos
>> 'world,'anyone
>> : cdrwa
>>
>> Why is the zookeeper node empty?  Is this the reason the  master and
>> slaves are not connecting?
>>
>> 2015-09-04 14:56 GMT-07:00 craig w :
>>
>>> No problem, they have a "downloads" link inn their menu:
>>> https://mesosphere.com/downloads/
>>> On Sep 4, 2015 5:43 PM, "Stephen Boesch"  wrote:
>>>
 @Craig . That is an incomplete answer - given that such links are not
 presented in an obvious manner .  Maybe you managed to find  a link on
 their site that provides prebuilt for Centos7: if so then please share it.


 I had previously found a link on their site for prebuilt binaries but
 is based on using CDH4 (which is not possible for my company). It is also
 old.

 https://docs.mesosphere.com/tutorials/install_centos_rhel/


 2015-09-04 14:27 GMT-07:00 craig w :

> Mesosphere has packages prebuilt, go to their site to find how to
> install
> On Sep 4, 2015 5:11 PM, "Stephen Boesch"  wrote:
>
>>
>> After following the directions here:
>> http://mesos.apache.org/gettingstarted/
>>
>> Which for centos7 includes the following:
>>
>>
>>
>>
>>   # Change working directory.
>> $ cd mesos
>>
>> # Bootstrap (Only required if building from git repository).
>> $ ./bootstrap
>>
>> # Configure and build.
>> $ mkdir build
>> $ cd build
>> $ ../configure
>> $ make
>>
>> In order to speed up the build and reduce verbosity of the logs, you
>> can append-j  V=0 to make.
>>
>> # Run test suite.
>> $ make check
>>
>> # Install (Optional).
>> $ make install
>>
>>
>>
>> But the installation is not correct afterwards: here is the bin
>> directory:
>>
>> $ ll bin
>> total 92
>> -rw-r--r--.  1 stack stack 1769 Jul 17 23:14
>> valgrind-mesos-tests.sh.in
>> -rw-r--r--.  1 stack stack 1769 Jul 17 23:14
>> valgrind-mesos-slave.sh.in
>> -rw-r--r--.  1 stack stack 1772 Jul 17 23:14
>> valgrind-mesos-master.sh.in
>> -rw-r--r--.  1 stack stack 1769 Jul 17 23:14
>> valgrind-mesos-local.sh.in
>> -rw-r--r--.  1 stack stack 1026 Jul 17 23:14 mesos-tests.sh.in
>> -rw-r--r--.  1 stack stack  901 Jul 17 23:14 mesos-tests-flags.sh.in
>> -rw-r--r--.  1