Re: Resource Allocation Question

[Vinod Kone]

The DRF algorithm works by looking at one slave's resource at a time. If a
slave's resource is filtered by a framework (due to declining), that
framework will not be considered a candidate for DRF for that resource. So
in your example, if Framework2 rejects, Framework1 should get the offer.

On Tue, Jul 7, 2015 at 3:45 PM, Ying Ji  wrote:

> Hey, Mesos experts:
>
>  The default allocation policy for mesos is DRF. Assume the dominant
> share for Framework1 is 20%, and the dominant share for Framework2 is 0%.
> So, Framework2 will receive next shares of resource offer which will
> increase the its dominant share to 10%. Since framework 2 continues to
> have the lower dominant share, it receives the next shares of resource
> offers. But somehow, the framework2 rejects the offers, in that case its
> dominant share is not changed.  So, does the framework2 will still receives
> the next shares of resource offers from master ? If framework2 keeps
> rejecting the offers, does this will starve the framework1 ?
>
>
> Thanks
>
> Ying
>

regarding task resource usage

[Badal Naik]

Hello Mesos,
i worked with mesos/docker since some days it works like a charm.I have a 
question regarding task resource usage in slaves:

If i have 3 slaves:
Slave a:  8 cores 
Slave b: 16 cores
slave c : 4 cores

And if i start a task via marathon with 0.1 cpus and 3 instances than how it 
will actually consume cpu on 3 different nodes?

e.g. : 0.1 of 8 core for slave a , o.1 of 16 core in slave b , o.1 of 4 core in 
slave-c?

Kindly Please help me for this.

Re: [RESULT] [VOTE] Release Apache Mesos 0.23.0 (rc1)

[Marco Massenzio]

As a general rule, we should not include anything other than the fixes in an 
RC, to avoid introducing further bugs in a never-ending cycle.




Please keep the cherry-picking strictly limited to a very narrow set (which I'm 
sure you're already doing, but your email seemed to imply otherwise ;-)




Thanks!



—
Sent from Mailbox

On Tue, Jul 7, 2015 at 3:56 PM, Adam Bordelon  wrote:

> In case it wasn't obvious, rc1 did not pass the vote, due to a few build
> and unit test issues.
> Most of those fixes have been committed, so we will cut rc2 when the last
> blocker is resolved.
> This is your last chance to get any recently committed patches or resolved
> issues into 0.23.0.
> I am tracking the 0.23.0-rc2 cherry picks in
> https://docs.google.com/spreadsheets/d/14yUtwfU0mGQ7x7UcjfzZg2o1TuRMkn5SvJvetARM7JQ/edit#gid=0
> Please contact me ASAP if you want anything else included.
> Thanks,
> -Adam-
> P.S. 0.23 Dashboard is still in action:
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12326227
> On Tue, Jul 7, 2015 at 1:59 PM, Adam Bordelon  wrote:
>> > -1 (non-binding) Network isolator will not compile.
>> https://issues.apache.org/jira/browse/MESOS-3002
>>
>> The changes for MESOS-2800
>>  to "Rename
>> Option::get(const T& _t) to getOrElse()" happened after the 0.23.0-rc1
>> cut and are not planned for cherry-picking into the release.
>> The Fix Version of MESOS-2800
>>  is 0.24.0, so the
>> Affects Version of MESOS-3002
>>  is really 0.24.0, and
>> hence its Target Version should also be 0.24.0.
>> Please let me know otherwise if you actually saw this build error when
>> building from the 0.23.0-rc1 tag.
>>
>> On Tue, Jul 7, 2015 at 11:48 AM, Paul Brett  wrote:
>>
>>> -1 (non-binding) Network isolator will not compile.
>>> https://issues.apache.org/jira/browse/MESOS-3002
>>>
>>>
>>> On Tue, Jul 7, 2015 at 11:38 AM, Alexander Rojas >> > wrote:
>>>
 +1 (non-binding)

 Ubuntu Server 15.04 gcc 4.9.2 and clang 3.6.0

 OS X Yosemite clang Apple LLVM based on 3.6.0


 On 06 Jul 2015, at 21:14, Jörg Schad  wrote:

 After more testing:
 -1 (non-binding)
 Docker tests failing on CentOS Linux release 7.1.1503 (Core) , Tim is
 already on the issue (see MESOS-2996)


 On Mon, Jul 6, 2015 at 8:59 PM, Kapil Arya  wrote:

> +1 (non-binding)
>
> OpenSUSE Tumbleweed, Linux 4.0.3 / gcc 4.8.3
>
> On Mon, Jul 6, 2015 at 2:33 PM, Ben Whitehead <
> ben.whiteh...@mesosphere.io> wrote:
>
>> +1 (non-binding)
>>
>> openSUSE 13.2 Linux 3.16.7 / gcc-4.8.3
>> Tested running Marathon 0.9.0-RC3 and Cassandra on Mesos
>> 0.1.1-SNAPSHOT.
>>
>> On Mon, Jul 6, 2015 at 6:57 AM, Till Toenshoff 
>> wrote:
>>
>>> Even though Alex has IMHO already “busted” this vote ;) .. THANKS
>>> ALEX! … ,
>>> here are my results.
>>>
>>> +1
>>>
>>> OS 10.10.4 (14E46) + Apple LLVM version 6.1.0 (clang-602.0.53) (based
>>> on LLVM 3.6.0svn), make check -> OK
>>> Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-32-generic x86_64) + gcc (Ubuntu
>>> 4.8.2-19ubuntu1) 4.8.2, make check -> OK
>>>
>>>
>>>
>>>
>>> On Jul 6, 2015, at 3:22 PM, Alex Rukletsov 
>>> wrote:
>>>
>>> -1
>>>
>>> Compilation error on Mac OS 10.10.4 with clang 3.5, which is
>>> supported according to release notes.
>>> More details: https://issues.apache.org/jira/browse/MESOS-2991
>>>
>>> On Mon, Jul 6, 2015 at 11:55 AM, Jörg Schad 
>>> wrote:
>>>
 P.S. to my prior +1
 Tested on ubuntu-trusty-14.04 including docker.

 On Sun, Jul 5, 2015 at 6:44 PM, Jörg Schad 
 wrote:

> +1
>
> On Sun, Jul 5, 2015 at 4:36 PM, Nikolaos Ballas neXus <
> nikolaos.bal...@nexusgroup.com> wrote:
>
>>  +1
>>
>>
>>
>>  Sent from my Samsung device
>>
>>
>>  Original message 
>> From: tommy xiao 
>> Date: 05/07/2015 15:14 (GMT+01:00)
>> To: user@mesos.apache.org
>> Subject: Re: [VOTE] Release Apache Mesos 0.23.0 (rc1)
>>
>>  +1
>>
>> 2015-07-04 12:32 GMT+08:00 Weitao :
>>
>>>  +1
>>>
>>> 发自我的 iPhone
>>>
>>> 在 2015年7月4日，09:41，Marco Massenzio  写道：
>>>
>>>   +1
>>>
>>>  *Marco Massenzio*
>>> *Distributed Systems Engineer*
>>>
>>> On Fri, Jul 3, 2015 at 12:25 PM, Adam Bordelon <
>>> a...@mesosphere.io> wrote:
>>>
 Hello Mesos community,

 Please vote on releasing the following candidate as Apache Mesos
 0.23.0.

 0.

[RESULT] [VOTE] Release Apache Mesos 0.23.0 (rc1)

[Adam Bordelon]

In case it wasn't obvious, rc1 did not pass the vote, due to a few build
and unit test issues.
Most of those fixes have been committed, so we will cut rc2 when the last
blocker is resolved.
This is your last chance to get any recently committed patches or resolved
issues into 0.23.0.
I am tracking the 0.23.0-rc2 cherry picks in
https://docs.google.com/spreadsheets/d/14yUtwfU0mGQ7x7UcjfzZg2o1TuRMkn5SvJvetARM7JQ/edit#gid=0
Please contact me ASAP if you want anything else included.

Thanks,
-Adam-

P.S. 0.23 Dashboard is still in action:
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12326227

On Tue, Jul 7, 2015 at 1:59 PM, Adam Bordelon  wrote:

> > -1 (non-binding) Network isolator will not compile.
> https://issues.apache.org/jira/browse/MESOS-3002
>
> The changes for MESOS-2800
>  to "Rename
> Option::get(const T& _t) to getOrElse()" happened after the 0.23.0-rc1
> cut and are not planned for cherry-picking into the release.
> The Fix Version of MESOS-2800
>  is 0.24.0, so the
> Affects Version of MESOS-3002
>  is really 0.24.0, and
> hence its Target Version should also be 0.24.0.
> Please let me know otherwise if you actually saw this build error when
> building from the 0.23.0-rc1 tag.
>
> On Tue, Jul 7, 2015 at 11:48 AM, Paul Brett  wrote:
>
>> -1 (non-binding) Network isolator will not compile.
>> https://issues.apache.org/jira/browse/MESOS-3002
>>
>>
>> On Tue, Jul 7, 2015 at 11:38 AM, Alexander Rojas > > wrote:
>>
>>> +1 (non-binding)
>>>
>>> Ubuntu Server 15.04 gcc 4.9.2 and clang 3.6.0
>>>
>>> OS X Yosemite clang Apple LLVM based on 3.6.0
>>>
>>>
>>> On 06 Jul 2015, at 21:14, Jörg Schad  wrote:
>>>
>>> After more testing:
>>> -1 (non-binding)
>>> Docker tests failing on CentOS Linux release 7.1.1503 (Core) , Tim is
>>> already on the issue (see MESOS-2996)
>>>
>>>
>>> On Mon, Jul 6, 2015 at 8:59 PM, Kapil Arya  wrote:
>>>
 +1 (non-binding)

 OpenSUSE Tumbleweed, Linux 4.0.3 / gcc 4.8.3

 On Mon, Jul 6, 2015 at 2:33 PM, Ben Whitehead <
 ben.whiteh...@mesosphere.io> wrote:

> +1 (non-binding)
>
> openSUSE 13.2 Linux 3.16.7 / gcc-4.8.3
> Tested running Marathon 0.9.0-RC3 and Cassandra on Mesos
> 0.1.1-SNAPSHOT.
>
> On Mon, Jul 6, 2015 at 6:57 AM, Till Toenshoff 
> wrote:
>
>> Even though Alex has IMHO already “busted” this vote ;) .. THANKS
>> ALEX! … ,
>> here are my results.
>>
>> +1
>>
>> OS 10.10.4 (14E46) + Apple LLVM version 6.1.0 (clang-602.0.53) (based
>> on LLVM 3.6.0svn), make check -> OK
>> Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-32-generic x86_64) + gcc (Ubuntu
>> 4.8.2-19ubuntu1) 4.8.2, make check -> OK
>>
>>
>>
>>
>> On Jul 6, 2015, at 3:22 PM, Alex Rukletsov 
>> wrote:
>>
>> -1
>>
>> Compilation error on Mac OS 10.10.4 with clang 3.5, which is
>> supported according to release notes.
>> More details: https://issues.apache.org/jira/browse/MESOS-2991
>>
>> On Mon, Jul 6, 2015 at 11:55 AM, Jörg Schad 
>> wrote:
>>
>>> P.S. to my prior +1
>>> Tested on ubuntu-trusty-14.04 including docker.
>>>
>>> On Sun, Jul 5, 2015 at 6:44 PM, Jörg Schad 
>>> wrote:
>>>
 +1

 On Sun, Jul 5, 2015 at 4:36 PM, Nikolaos Ballas neXus <
 nikolaos.bal...@nexusgroup.com> wrote:

>  +1
>
>
>
>  Sent from my Samsung device
>
>
>  Original message 
> From: tommy xiao 
> Date: 05/07/2015 15:14 (GMT+01:00)
> To: user@mesos.apache.org
> Subject: Re: [VOTE] Release Apache Mesos 0.23.0 (rc1)
>
>  +1
>
> 2015-07-04 12:32 GMT+08:00 Weitao :
>
>>  +1
>>
>> 发自我的 iPhone
>>
>> 在 2015年7月4日，09:41，Marco Massenzio  写道：
>>
>>   +1
>>
>>  *Marco Massenzio*
>> *Distributed Systems Engineer*
>>
>> On Fri, Jul 3, 2015 at 12:25 PM, Adam Bordelon <
>> a...@mesosphere.io> wrote:
>>
>>> Hello Mesos community,
>>>
>>> Please vote on releasing the following candidate as Apache Mesos
>>> 0.23.0.
>>>
>>> 0.23.0 includes the following:
>>>
>>> 
>>>  - Per-container network isolation
>>> - Upgraded minimum required compilers to GCC 4.8+ or clang 3.5+.
>>> - Dockerized slaves will properly recover Docker containers upon
>>> failover.
>>>
>>> as well as experimental support for:
>>>  - Fetcher Caching
>>>  - Revocable Resources
>>>  - SSL encryption
>>>  - Persistent Volu

Resource Allocation Question

[Ying Ji]

Hey, Mesos experts:

 The default allocation policy for mesos is DRF. Assume the dominant
share for Framework1 is 20%, and the dominant share for Framework2 is 0%.
So, Framework2 will receive next shares of resource offer which will
increase the its dominant share to 10%. Since framework 2 continues to have
the lower dominant share, it receives the next shares of resource offers.
But somehow, the framework2 rejects the offers, in that case its dominant
share is not changed.  So, does the framework2 will still receives the next
shares of resource offers from master ? If framework2 keeps rejecting the
offers, does this will starve the framework1 ?


Thanks

Ying

Re: [VOTE] Release Apache Mesos 0.23.0 (rc1)

[Adam Bordelon]

> -1 (non-binding) Network isolator will not compile.
https://issues.apache.org/jira/browse/MESOS-3002

The changes for MESOS-2800
 to "Rename
Option::get(const T& _t) to getOrElse()" happened after the 0.23.0-rc1
cut and are not planned for cherry-picking into the release.
The Fix Version of MESOS-2800
 is 0.24.0, so the
Affects Version of MESOS-3002
 is really 0.24.0, and
hence its Target Version should also be 0.24.0.
Please let me know otherwise if you actually saw this build error when
building from the 0.23.0-rc1 tag.

On Tue, Jul 7, 2015 at 11:48 AM, Paul Brett  wrote:

> -1 (non-binding) Network isolator will not compile.
> https://issues.apache.org/jira/browse/MESOS-3002
>
>
> On Tue, Jul 7, 2015 at 11:38 AM, Alexander Rojas 
> wrote:
>
>> +1 (non-binding)
>>
>> Ubuntu Server 15.04 gcc 4.9.2 and clang 3.6.0
>>
>> OS X Yosemite clang Apple LLVM based on 3.6.0
>>
>>
>> On 06 Jul 2015, at 21:14, Jörg Schad  wrote:
>>
>> After more testing:
>> -1 (non-binding)
>> Docker tests failing on CentOS Linux release 7.1.1503 (Core) , Tim is
>> already on the issue (see MESOS-2996)
>>
>>
>> On Mon, Jul 6, 2015 at 8:59 PM, Kapil Arya  wrote:
>>
>>> +1 (non-binding)
>>>
>>> OpenSUSE Tumbleweed, Linux 4.0.3 / gcc 4.8.3
>>>
>>> On Mon, Jul 6, 2015 at 2:33 PM, Ben Whitehead <
>>> ben.whiteh...@mesosphere.io> wrote:
>>>
 +1 (non-binding)

 openSUSE 13.2 Linux 3.16.7 / gcc-4.8.3
 Tested running Marathon 0.9.0-RC3 and Cassandra on Mesos 0.1.1-SNAPSHOT.

 On Mon, Jul 6, 2015 at 6:57 AM, Till Toenshoff 
 wrote:

> Even though Alex has IMHO already “busted” this vote ;) .. THANKS
> ALEX! … ,
> here are my results.
>
> +1
>
> OS 10.10.4 (14E46) + Apple LLVM version 6.1.0 (clang-602.0.53) (based
> on LLVM 3.6.0svn), make check -> OK
> Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-32-generic x86_64) + gcc (Ubuntu
> 4.8.2-19ubuntu1) 4.8.2, make check -> OK
>
>
>
>
> On Jul 6, 2015, at 3:22 PM, Alex Rukletsov 
> wrote:
>
> -1
>
> Compilation error on Mac OS 10.10.4 with clang 3.5, which is supported
> according to release notes.
> More details: https://issues.apache.org/jira/browse/MESOS-2991
>
> On Mon, Jul 6, 2015 at 11:55 AM, Jörg Schad 
> wrote:
>
>> P.S. to my prior +1
>> Tested on ubuntu-trusty-14.04 including docker.
>>
>> On Sun, Jul 5, 2015 at 6:44 PM, Jörg Schad 
>> wrote:
>>
>>> +1
>>>
>>> On Sun, Jul 5, 2015 at 4:36 PM, Nikolaos Ballas neXus <
>>> nikolaos.bal...@nexusgroup.com> wrote:
>>>
  +1



  Sent from my Samsung device


  Original message 
 From: tommy xiao 
 Date: 05/07/2015 15:14 (GMT+01:00)
 To: user@mesos.apache.org
 Subject: Re: [VOTE] Release Apache Mesos 0.23.0 (rc1)

  +1

 2015-07-04 12:32 GMT+08:00 Weitao :

>  +1
>
> 发自我的 iPhone
>
> 在 2015年7月4日，09:41，Marco Massenzio  写道：
>
>   +1
>
>  *Marco Massenzio*
> *Distributed Systems Engineer*
>
> On Fri, Jul 3, 2015 at 12:25 PM, Adam Bordelon  > wrote:
>
>> Hello Mesos community,
>>
>> Please vote on releasing the following candidate as Apache Mesos
>> 0.23.0.
>>
>> 0.23.0 includes the following:
>>
>> 
>>  - Per-container network isolation
>> - Upgraded minimum required compilers to GCC 4.8+ or clang 3.5+.
>> - Dockerized slaves will properly recover Docker containers upon
>> failover.
>>
>> as well as experimental support for:
>>  - Fetcher Caching
>>  - Revocable Resources
>>  - SSL encryption
>>  - Persistent Volumes
>>  - Dynamic Reservations
>>
>> 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.23.0-rc1
>>
>> 
>>
>> The candidate for Mesos 0.23.0 release is available at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc1/mesos-0.23.0.tar.gz
>>
>> The tag to be voted on is 0.23.0-rc1:
>>
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.23.0-rc1
>>
>> The MD5 checksum of the tarball can be found at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc1/mesos-0.23.0.tar.gz.md5
>>
>> The 

Re: Multi-mastersD

[CCAAT]

I'm glad to know it is easy, that's what I was hoping for.


I want to keep the (3+) masters on line 7/24/365 but have different 
"teams" of slave that do different (industrial) tasks. Each team would 
be geographically close, if not on the same power buss. I would think
this is routine, but I have not tried it yet. Sure, the number of 
masters will expand as needed, but one pool of masters. Many many pools 
of mesos slaves with various abilities, in diverse if not extremely 
remote locations.



So it's been done? Experiences?  Many of these 'slave processor teams' 
will sleep for significant periods, if that matters. Think of it as a 
very distributed cluster with very diversified hardware and task 
requests que. Rarely working on a single BIG problem

but still with that Big problem, one team capability.


Any suggestions for long term sleep issues of slaves? Upgrade scheduling 
? Data consistency once a team is awakened?



James



On 07/07/2015 10:08 AM, Marco Massenzio wrote:

(I'm sure I'm missing something here, so please forgive if I'm stating
the obvious)

This is actually very well supported right now: you can use "slave
attributes" (if, eg, you want to name the various clusters differently
and launch tasks according to those criteria) that would be passed on to
the Frameworks along with the resource offers: the frameworks could then
decide whether to accept the offer and launch tasks based on whatever
logic you want to implement.

You could use something like "--attributes="cluster:01z99;
os:ubuntu-14-04; jdk:8" or whatever makes sense.

/Marco Massenzio/
/Distributed Systems Engineer/

On Tue, Jul 7, 2015 at 8:55 AM, CCAAT mailto:cc...@tampabay.rr.com>> wrote:

Hello team_mesos,

Is there any reason one set of (3) masters cannot talk to and manage
several (many) different slave clusters of (3)? These slave clusters
would be different arch, different mixes of resources and be running
different frameworks, but all share/use the same (3) masters.


Ideas on how to architect this experiment, would be keenly appreciated.


James

Re: [VOTE] Release Apache Mesos 0.23.0 (rc1)

[Paul Brett]

-1 (non-binding) Network isolator will not compile.
https://issues.apache.org/jira/browse/MESOS-3002


On Tue, Jul 7, 2015 at 11:38 AM, Alexander Rojas 
wrote:

> +1 (non-binding)
>
> Ubuntu Server 15.04 gcc 4.9.2 and clang 3.6.0
>
> OS X Yosemite clang Apple LLVM based on 3.6.0
>
>
> On 06 Jul 2015, at 21:14, Jörg Schad  wrote:
>
> After more testing:
> -1 (non-binding)
> Docker tests failing on CentOS Linux release 7.1.1503 (Core) , Tim is
> already on the issue (see MESOS-2996)
>
>
> On Mon, Jul 6, 2015 at 8:59 PM, Kapil Arya  wrote:
>
>> +1 (non-binding)
>>
>> OpenSUSE Tumbleweed, Linux 4.0.3 / gcc 4.8.3
>>
>> On Mon, Jul 6, 2015 at 2:33 PM, Ben Whitehead <
>> ben.whiteh...@mesosphere.io> wrote:
>>
>>> +1 (non-binding)
>>>
>>> openSUSE 13.2 Linux 3.16.7 / gcc-4.8.3
>>> Tested running Marathon 0.9.0-RC3 and Cassandra on Mesos 0.1.1-SNAPSHOT.
>>>
>>> On Mon, Jul 6, 2015 at 6:57 AM, Till Toenshoff  wrote:
>>>
 Even though Alex has IMHO already “busted” this vote ;) .. THANKS ALEX!
 … ,
 here are my results.

 +1

 OS 10.10.4 (14E46) + Apple LLVM version 6.1.0 (clang-602.0.53) (based
 on LLVM 3.6.0svn), make check -> OK
 Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-32-generic x86_64) + gcc (Ubuntu
 4.8.2-19ubuntu1) 4.8.2, make check -> OK




 On Jul 6, 2015, at 3:22 PM, Alex Rukletsov  wrote:

 -1

 Compilation error on Mac OS 10.10.4 with clang 3.5, which is supported
 according to release notes.
 More details: https://issues.apache.org/jira/browse/MESOS-2991

 On Mon, Jul 6, 2015 at 11:55 AM, Jörg Schad 
 wrote:

> P.S. to my prior +1
> Tested on ubuntu-trusty-14.04 including docker.
>
> On Sun, Jul 5, 2015 at 6:44 PM, Jörg Schad 
> wrote:
>
>> +1
>>
>> On Sun, Jul 5, 2015 at 4:36 PM, Nikolaos Ballas neXus <
>> nikolaos.bal...@nexusgroup.com> wrote:
>>
>>>  +1
>>>
>>>
>>>
>>>  Sent from my Samsung device
>>>
>>>
>>>  Original message 
>>> From: tommy xiao 
>>> Date: 05/07/2015 15:14 (GMT+01:00)
>>> To: user@mesos.apache.org
>>> Subject: Re: [VOTE] Release Apache Mesos 0.23.0 (rc1)
>>>
>>>  +1
>>>
>>> 2015-07-04 12:32 GMT+08:00 Weitao :
>>>
  +1

 发自我的 iPhone

 在 2015年7月4日，09:41，Marco Massenzio  写道：

   +1

  *Marco Massenzio*
 *Distributed Systems Engineer*

 On Fri, Jul 3, 2015 at 12:25 PM, Adam Bordelon 
 wrote:

> Hello Mesos community,
>
> Please vote on releasing the following candidate as Apache Mesos
> 0.23.0.
>
> 0.23.0 includes the following:
>
> 
>  - Per-container network isolation
> - Upgraded minimum required compilers to GCC 4.8+ or clang 3.5+.
> - Dockerized slaves will properly recover Docker containers upon
> failover.
>
> as well as experimental support for:
>  - Fetcher Caching
>  - Revocable Resources
>  - SSL encryption
>  - Persistent Volumes
>  - Dynamic Reservations
>
> 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.23.0-rc1
>
> 
>
> The candidate for Mesos 0.23.0 release is available at:
>
> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc1/mesos-0.23.0.tar.gz
>
> The tag to be voted on is 0.23.0-rc1:
>
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.23.0-rc1
>
> The MD5 checksum of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc1/mesos-0.23.0.tar.gz.md5
>
> The signature of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc1/mesos-0.23.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-1056
>
> Please vote on releasing this package as Apache Mesos 0.23.0!
>
> The vote is open until Fri July 10th, 12:00 PDT 2015 and passes if
> a majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 0.23.0
> [ ] -1 Do not release this package because ...
>
> Thanks,
>  -Adam-
>


>>>
>>>
>>>  --

Re: [VOTE] Release Apache Mesos 0.23.0 (rc1)

[Alexander Rojas]

+1 (non-binding)

Ubuntu Server 15.04 gcc 4.9.2 and clang 3.6.0

OS X Yosemite clang Apple LLVM based on 3.6.0

> On 06 Jul 2015, at 21:14, Jörg Schad  wrote:
> 
> After more testing:
> -1 (non-binding)
> Docker tests failing on CentOS Linux release 7.1.1503 (Core) , Tim is already 
> on the issue (see MESOS-2996)
> 
> 
> On Mon, Jul 6, 2015 at 8:59 PM, Kapil Arya  > wrote:
> +1 (non-binding)
> 
> OpenSUSE Tumbleweed, Linux 4.0.3 / gcc 4.8.3
> 
> On Mon, Jul 6, 2015 at 2:33 PM, Ben Whitehead  > wrote:
> +1 (non-binding)
> 
> openSUSE 13.2 Linux 3.16.7 / gcc-4.8.3
> Tested running Marathon 0.9.0-RC3 and Cassandra on Mesos 0.1.1-SNAPSHOT.
> 
> On Mon, Jul 6, 2015 at 6:57 AM, Till Toenshoff  > wrote:
> Even though Alex has IMHO already “busted” this vote ;) .. THANKS ALEX! … , 
> here are my results.
> 
> +1
> 
> OS 10.10.4 (14E46) + Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 
> 3.6.0svn), make check -> OK
> Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-32-generic x86_64) + gcc (Ubuntu 
> 4.8.2-19ubuntu1) 4.8.2, make check -> OK
> 
> 
> 
> 
>> On Jul 6, 2015, at 3:22 PM, Alex Rukletsov > > wrote:
>> 
>> -1
>> 
>> Compilation error on Mac OS 10.10.4 with clang 3.5, which is supported 
>> according to release notes.
>> More details: https://issues.apache.org/jira/browse/MESOS-2991 
>> 
>> 
>> On Mon, Jul 6, 2015 at 11:55 AM, Jörg Schad > > wrote:
>> P.S. to my prior +1
>> Tested on ubuntu-trusty-14.04 including docker.
>> 
>> On Sun, Jul 5, 2015 at 6:44 PM, Jörg Schad > > wrote:
>> +1
>> 
>> On Sun, Jul 5, 2015 at 4:36 PM, Nikolaos Ballas neXus 
>> mailto:nikolaos.bal...@nexusgroup.com>> 
>> wrote:
>> +1
>> 
>> 
>> 
>> Sent from my Samsung device
>> 
>> 
>>  Original message 
>> From: tommy xiao mailto:xia...@gmail.com>> 
>> Date: 05/07/2015 15:14 (GMT+01:00) 
>> To: user@mesos.apache.org  
>> Subject: Re: [VOTE] Release Apache Mesos 0.23.0 (rc1) 
>> 
>> +1
>> 
>> 2015-07-04 12:32 GMT+08:00 Weitao > >:
>> +1
>> 
>> 发自我的 iPhone
>> 
>> 在 2015年7月4日，09:41，Marco Massenzio > > 写道：
>> 
>>> +1
>>> 
>>> Marco Massenzio
>>> Distributed Systems Engineer
>>> 
>>> On Fri, Jul 3, 2015 at 12:25 PM, Adam Bordelon >> > wrote:
>>> Hello Mesos community,
>>> 
>>> Please vote on releasing the following candidate as Apache Mesos 0.23.0.
>>> 
>>> 0.23.0 includes the following:
>>> 
>>> - Per-container network isolation
>>> - Upgraded minimum required compilers to GCC 4.8+ or clang 3.5+.
>>> - Dockerized slaves will properly recover Docker containers upon failover.
>>> 
>>> as well as experimental support for:
>>> - Fetcher Caching
>>> - Revocable Resources
>>> - SSL encryption
>>> - Persistent Volumes
>>> - Dynamic Reservations
>>> 
>>> 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.23.0-rc1
>>>  
>>> 
>>> 
>>> 
>>> The candidate for Mesos 0.23.0 release is available at:
>>> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc1/mesos-0.23.0.tar.gz 
>>> 
>>> 
>>> The tag to be voted on is 0.23.0-rc1:
>>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.23.0-rc1 
>>> 
>>> 
>>> The MD5 checksum of the tarball can be found at:
>>> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc1/mesos-0.23.0.tar.gz.md5
>>>  
>>> 
>>> 
>>> The signature of the tarball can be found at:
>>> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc1/mesos-0.23.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-1056 
>>> 
>>> 
>>> Please vote on releasing this package as Apache Mesos 0.23.0!
>>> 
>>> The vote is open until Fri July 10th, 12:00 PDT 2015 and passes if a 
>>> majority of at least 3 +1 PMC votes are cast.
>>> 
>>> [ ] +1 Release this package as Apache Mesos 0.23.0
>>> [ ] -1 Do not release

RE: mesos-execute + docker_image

[Tom Arnfeld]

I've been using mesos-execute for a few little experiments, using docker 
images. The --docker_image flag will be passed straight through to mesos as the 
string to use for the actual image. There are no other options at present for 
specifying docker port mapping/networking/volume configuration through 
mesos-execute at the moment.


Tom.



--


Tom Arnfeld

Senior Developer // DueDil






On Tuesday, Jul 7, 2015 at 5:21 pm, Nikolaos Ballas neXus 
, wrote:



Search for containerizers in the manual on apache or mesosphere sites 





















Sent from my Samsung device











 Original message 


From: tommy xiao  


Date: 07/07/2015 18:14 (GMT+01:00) 


To: user@mesos.apache.org 


Subject: Re: mesos-execute + docker_image 




How about check marathon?



2015-07-07 22:26 GMT+08:00 Jürgen Jakobitsch 

:



hi,






i just installed mesos-0.22.0 (from the mesossphere repos) on centOS6.



can anyone point me into the right direction on how to run a docker image



inside mesos using mesos-execute plus the docker_image parameter.








also note that i would like to pass some parameters to the docker run command








any pointer really appreciated.








wkr j
















| Jürgen Jakobitsch,


| Software Developer


| Semantic Web Company GmbH


| Mariahilfer Straße 70 / Neubaugasse 1, Top 8


| A - 1070 Wien, Austria


| Mob +43 676 62 12 710 | Fax 

+43.1.402 12 35 - 22



COMPANY INFORMATION


| web       : http://www.semantic-web.at/


| foaf      : 

http://company.semantic-web.at/person/juergen_jakobitsch


PERSONAL INFORMATION


| web       : http://www.turnguard.com


| foaf      : http://www.turnguard.com/turnguard


| g+        : 

https://plus.google.com/111233759991616358206/posts


| skype     : jakobitsch-punkt


| xmlns:tg  = "http://www.turnguard.com/turnguard#";

































-- 
Deshi Xiao


Twitter: xds2000


E-mail: xiaods(AT)gmail.com

Re: [VOTE] Release Apache Mesos 0.23.0 (rc1)

[Ian Downes]

-1
Failing tests:
https://issues.apache.org/jira/browse/MESOS-2199
https://issues.apache.org/jira/browse/MESOS-3000

On Tue, Jul 7, 2015 at 8:52 AM, CCAAT  wrote:

> {++1} Non binding.
>
> Gentoo works great on x64. Mostly working on arm8v.
> Besides the more frequently release cycles keep the
> work interesting and moving at a refreshing pace.
> I.E. We've been on 0.22 too long..
>
>
> hth,
> James
>
>
>
>
> On 07/06/2015 02:14 PM, Jörg Schad wrote:
>
>> After more testing:
>> -1 (non-binding)
>> Docker tests failing on CentOS Linux release 7.1.1503 (Core) , Tim is
>> already on the issue (see MESOS-2996)
>>
>>
>> On Mon, Jul 6, 2015 at 8:59 PM, Kapil Arya > > wrote:
>>
>> +1 (non-binding)
>>
>> OpenSUSE Tumbleweed, Linux 4.0.3 / gcc 4.8.3
>>
>> On Mon, Jul 6, 2015 at 2:33 PM, Ben Whitehead
>> mailto:ben.whiteh...@mesosphere.io>>
>> wrote:
>>
>> +1 (non-binding)
>>
>> openSUSE 13.2 Linux 3.16.7 / gcc-4.8.3
>> Tested running Marathon 0.9.0-RC3 and Cassandra on Mesos
>> 0.1.1-SNAPSHOT.
>>
>> On Mon, Jul 6, 2015 at 6:57 AM, Till Toenshoff > > wrote:
>>
>> Even though Alex has IMHO already “busted” this vote ;) ..
>> THANKS ALEX! … ,
>> here are my results.
>>
>> +1
>>
>> OS 10.10.4 (14E46) + Apple LLVM version 6.1.0
>> (clang-602.0.53) (based on LLVM 3.6.0svn), make check -> OK
>> Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-32-generic x86_64)
>> + gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2, make check -> OK
>>
>>
>>
>>
>>  On Jul 6, 2015, at 3:22 PM, Alex Rukletsov
>>> mailto:a...@mesosphere.com>> wrote:
>>>
>>> -1
>>>
>>> Compilation error on Mac OS 10.10.4 with clang 3.5, which
>>> is supported according to release notes.
>>> More details:
>>> https://issues.apache.org/jira/browse/MESOS-2991
>>>
>>> On Mon, Jul 6, 2015 at 11:55 AM, Jörg Schad
>>> mailto:jo...@mesosphere.io>> wrote:
>>>
>>> P.S. to my prior +1
>>> Tested on ubuntu-trusty-14.04 including docker.
>>>
>>> On Sun, Jul 5, 2015 at 6:44 PM, Jörg Schad
>>> mailto:jo...@mesosphere.io>>
>>> wrote:
>>>
>>> +1
>>>
>>> On Sun, Jul 5, 2015 at 4:36 PM, Nikolaos Ballas
>>> neXus >> > wrote:
>>>
>>> +1
>>>
>>>
>>>
>>> Sent from my Samsung device
>>>
>>>
>>>  Original message 
>>> From: tommy xiao >> >
>>> Date: 05/07/2015 15:14 (GMT+01:00)
>>> To: user@mesos.apache.org
>>> 
>>> Subject: Re: [VOTE] Release Apache Mesos
>>> 0.23.0 (rc1)
>>>
>>> +1
>>>
>>> 2015-07-04 12:32 GMT+08:00 Weitao
>>> >> >:
>>>
>>> +1
>>>
>>> 发自我的 iPhone
>>>
>>> 在 2015年7月4日，09:41，Marco Massenzio
>>> >> > 写道：
>>>
>>>  +1

 /Marco Massenzio/
 /Distributed Systems Engineer/

 On Fri, Jul 3, 2015 at 12:25 PM, Adam
 Bordelon >>> > wrote:

 Hello Mesos community,

 Please vote on releasing the
 following candidate as Apache Mesos
 0.23.0.

 0.23.0 includes the following:

 
 - Per-container network isolation
 - Upgraded minimum required compilers
 to GCC 4.8+ or clang 3.5+.
 - Dockerized slaves will properly
 recover Docker containers upon failover.

 as well as experimental support for:
 - Fetcher Caching
 - Revocable Resources
 - SSL encryption
 - Persistent Volumes

Re: mesos-execute + docker_image

[Jürgen Jakobitsch]

I meant to say: marathon is not an option... wkrj

Am Dienstag, 7. Juli 2015 schrieb Jürgen Jakobitsch :

> Hi.
>
> Mesosphere is not an option for now. I want to run the docker image
> without it.
>
> I run all my slaves with containerizer option and also saw mesos-execute
> help. There's a possible parameter "docker_image" which i want to use.
> However i need to pass parameter to the docker image (eg. -p for the port,
> i'm trying to run virtuoso triple store inside mesos and the p param is
> needed for sparq endpoint's port). Also mesos-execute complains when i do
> not add a command parameter. How should that command look like, when using
> docker_image param?
>
> Does anybody know how to start a docker image using mesos-execute?
>
> Wkr j
>
> Am Dienstag, 7. Juli 2015 schrieb Nikolaos Ballas neXus :
>
>>  Search for containerizers in the manual on apache or mesosphere sites
>>
>>
>>
>>  Sent from my Samsung device
>>
>>
>>  Original message 
>> From: tommy xiao 
>> Date: 07/07/2015 18:14 (GMT+01:00)
>> To: user@mesos.apache.org
>> Subject: Re: mesos-execute + docker_image
>>
>>  How about check marathon?
>>
>> 2015-07-07 22:26 GMT+08:00 Jürgen Jakobitsch <
>> j.jakobit...@semantic-web.at>:
>>
>>> hi,
>>>
>>>  i just installed mesos-0.22.0 (from the mesossphere repos) on centOS6.
>>> can anyone point me into the right direction on how to run a docker image
>>> inside mesos using mesos-execute plus the docker_image parameter.
>>>
>>>  also note that i would like to pass some parameters to the docker run
>>> command
>>>
>>>  any pointer really appreciated.
>>>
>>>  wkr j
>>>
>>>
>>>  | Jürgen Jakobitsch,
>>> | Software Developer
>>> | Semantic Web Company GmbH
>>> | Mariahilfer Straße 70 / Neubaugasse 1, Top 8
>>> | A - 1070 Wien, Austria
>>> | Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22
>>>
>>> COMPANY INFORMATION
>>> | web   : http://www.semantic-web.at/
>>> | foaf  : http://company.semantic-web.at/person/juergen_jakobitsch
>>> PERSONAL INFORMATION
>>> | web   : http://www.turnguard.com
>>> | foaf  : http://www.turnguard.com/turnguard
>>> | g+: https://plus.google.com/111233759991616358206/posts
>>> | skype : jakobitsch-punkt
>>> | xmlns:tg  = "http://www.turnguard.com/turnguard#";
>>>
>>
>>
>>
>>  --
>> Deshi Xiao
>> Twitter: xds2000
>> E-mail: xiaods(AT)gmail.com
>>
>
>
> --
> | Jürgen Jakobitsch,
> | Software Developer
> | Semantic Web Company GmbH
> | Mariahilfer Straße 70 / Neubaugasse 1, Top 8
> | A - 1070 Wien, Austria
> | Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22
>
> COMPANY INFORMATION
> | web   : http://www.semantic-web.at/
> | foaf  : http://company.semantic-web.at/person/juergen_jakobitsch
> PERSONAL INFORMATION
> | web   : http://www.turnguard.com
> | foaf  : http://www.turnguard.com/turnguard
> | g+: https://plus.google.com/111233759991616358206/posts
> | skype : jakobitsch-punkt
> | xmlns:tg  = "http://www.turnguard.com/turnguard#";
>
>

-- 
| Jürgen Jakobitsch,
| Software Developer
| Semantic Web Company GmbH
| Mariahilfer Straße 70 / Neubaugasse 1, Top 8
| A - 1070 Wien, Austria
| Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22

COMPANY INFORMATION
| web   : http://www.semantic-web.at/
| foaf  : http://company.semantic-web.at/person/juergen_jakobitsch
PERSONAL INFORMATION
| web   : http://www.turnguard.com
| foaf  : http://www.turnguard.com/turnguard
| g+: https://plus.google.com/111233759991616358206/posts
| skype : jakobitsch-punkt
| xmlns:tg  = "http://www.turnguard.com/turnguard#";

Re: mesos-execute + docker_image

[Jürgen Jakobitsch]

Hi.

Mesosphere is not an option for now. I want to run the docker image without
it.

I run all my slaves with containerizer option and also saw mesos-execute
help. There's a possible parameter "docker_image" which i want to use.
However i need to pass parameter to the docker image (eg. -p for the port,
i'm trying to run virtuoso triple store inside mesos and the p param is
needed for sparq endpoint's port). Also mesos-execute complains when i do
not add a command parameter. How should that command look like, when using
docker_image param?

Does anybody know how to start a docker image using mesos-execute?

Wkr j

Am Dienstag, 7. Juli 2015 schrieb Nikolaos Ballas neXus :

>  Search for containerizers in the manual on apache or mesosphere sites
>
>
>
>  Sent from my Samsung device
>
>
>  Original message 
> From: tommy xiao  >
> Date: 07/07/2015 18:14 (GMT+01:00)
> To: user@mesos.apache.org
> 
> Subject: Re: mesos-execute + docker_image
>
>  How about check marathon?
>
> 2015-07-07 22:26 GMT+08:00 Jürgen Jakobitsch  >:
>
>> hi,
>>
>>  i just installed mesos-0.22.0 (from the mesossphere repos) on centOS6.
>> can anyone point me into the right direction on how to run a docker image
>> inside mesos using mesos-execute plus the docker_image parameter.
>>
>>  also note that i would like to pass some parameters to the docker run
>> command
>>
>>  any pointer really appreciated.
>>
>>  wkr j
>>
>>
>>  | Jürgen Jakobitsch,
>> | Software Developer
>> | Semantic Web Company GmbH
>> | Mariahilfer Straße 70 / Neubaugasse 1, Top 8
>> | A - 1070 Wien, Austria
>> | Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22
>>
>> COMPANY INFORMATION
>> | web   : http://www.semantic-web.at/
>> | foaf  : http://company.semantic-web.at/person/juergen_jakobitsch
>> PERSONAL INFORMATION
>> | web   : http://www.turnguard.com
>> | foaf  : http://www.turnguard.com/turnguard
>> | g+: https://plus.google.com/111233759991616358206/posts
>> | skype : jakobitsch-punkt
>> | xmlns:tg  = "http://www.turnguard.com/turnguard#";
>>
>
>
>
>  --
> Deshi Xiao
> Twitter: xds2000
> E-mail: xiaods(AT)gmail.com
>


-- 
| Jürgen Jakobitsch,
| Software Developer
| Semantic Web Company GmbH
| Mariahilfer Straße 70 / Neubaugasse 1, Top 8
| A - 1070 Wien, Austria
| Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22

COMPANY INFORMATION
| web   : http://www.semantic-web.at/
| foaf  : http://company.semantic-web.at/person/juergen_jakobitsch
PERSONAL INFORMATION
| web   : http://www.turnguard.com
| foaf  : http://www.turnguard.com/turnguard
| g+: https://plus.google.com/111233759991616358206/posts
| skype : jakobitsch-punkt
| xmlns:tg  = "http://www.turnguard.com/turnguard#";

RE: mesos-execute + docker_image

[Nikolaos Ballas neXus]

Search for containerizers in the manual on apache or mesosphere sites



Sent from my Samsung device


 Original message 
From: tommy xiao 
Date: 07/07/2015 18:14 (GMT+01:00)
To: user@mesos.apache.org
Subject: Re: mesos-execute + docker_image

How about check marathon?

2015-07-07 22:26 GMT+08:00 J?rgen Jakobitsch 
mailto:j.jakobit...@semantic-web.at>>:
hi,

i just installed mesos-0.22.0 (from the mesossphere repos) on centOS6.
can anyone point me into the right direction on how to run a docker image
inside mesos using mesos-execute plus the docker_image parameter.

also note that i would like to pass some parameters to the docker run command

any pointer really appreciated.

wkr j


| J?rgen Jakobitsch,
| Software Developer
| Semantic Web Company GmbH
| Mariahilfer Stra?e 70 / Neubaugasse 1, Top 8
| A - 1070 Wien, Austria
| Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22

COMPANY INFORMATION
| web   : http://www.semantic-web.at/
| foaf  : http://company.semantic-web.at/person/juergen_jakobitsch
PERSONAL INFORMATION
| web   : http://www.turnguard.com
| foaf  : http://www.turnguard.com/turnguard
| g+: https://plus.google.com/111233759991616358206/posts
| skype : jakobitsch-punkt
| xmlns:tg  = "http://www.turnguard.com/turnguard#";



--
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com

Re: mesos-execute + docker_image

[Tim Chen]

Hi there,

What kind of parameters do you like to pass to mesos-execute?

You can run mesos-execute --help and it shows you all the available
parameters.

Tim

On Tue, Jul 7, 2015 at 7:26 AM, Jürgen Jakobitsch <
j.jakobit...@semantic-web.at> wrote:

> hi,
>
> i just installed mesos-0.22.0 (from the mesossphere repos) on centOS6.
> can anyone point me into the right direction on how to run a docker image
> inside mesos using mesos-execute plus the docker_image parameter.
>
> also note that i would like to pass some parameters to the docker run
> command
>
> any pointer really appreciated.
>
> wkr j
>
>
> | Jürgen Jakobitsch,
> | Software Developer
> | Semantic Web Company GmbH
> | Mariahilfer Straße 70 / Neubaugasse 1, Top 8
> | A - 1070 Wien, Austria
> | Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22
>
> COMPANY INFORMATION
> | web   : http://www.semantic-web.at/
> | foaf  : http://company.semantic-web.at/person/juergen_jakobitsch
> PERSONAL INFORMATION
> | web   : http://www.turnguard.com
> | foaf  : http://www.turnguard.com/turnguard
> | g+: https://plus.google.com/111233759991616358206/posts
> | skype : jakobitsch-punkt
> | xmlns:tg  = "http://www.turnguard.com/turnguard#";
>

Re: mesos-execute + docker_image

[tommy xiao]

How about check marathon?

2015-07-07 22:26 GMT+08:00 Jürgen Jakobitsch :

> hi,
>
> i just installed mesos-0.22.0 (from the mesossphere repos) on centOS6.
> can anyone point me into the right direction on how to run a docker image
> inside mesos using mesos-execute plus the docker_image parameter.
>
> also note that i would like to pass some parameters to the docker run
> command
>
> any pointer really appreciated.
>
> wkr j
>
>
> | Jürgen Jakobitsch,
> | Software Developer
> | Semantic Web Company GmbH
> | Mariahilfer Straße 70 / Neubaugasse 1, Top 8
> | A - 1070 Wien, Austria
> | Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22
>
> COMPANY INFORMATION
> | web   : http://www.semantic-web.at/
> | foaf  : http://company.semantic-web.at/person/juergen_jakobitsch
> PERSONAL INFORMATION
> | web   : http://www.turnguard.com
> | foaf  : http://www.turnguard.com/turnguard
> | g+: https://plus.google.com/111233759991616358206/posts
> | skype : jakobitsch-punkt
> | xmlns:tg  = "http://www.turnguard.com/turnguard#";
>



-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com

Re: Java detector for mess masters and leader

[Donald Laidlaw]

Thank you all.

I will use the Curator recipe, since I already use Curator for a bunch of other 
things. 

If curator can find the leader and the participants that is good enough. 
Otherwise I will parse the protocol buffer contents, and provide a way to parse 
the future son contents when that happens.

I’ll reply again with the results of using the Curator recipe to get the leader 
and participants.

Best regards,
-Don

> On Jul 7, 2015, at 11:04 AM, Dick Davies  wrote:
> 
> The active master has a flag set in  /metrics/snapshot  :
> "master/elected" which is 1 for the active
> master and 0 otherwise, so it's easy enough to only load the metrics
> from the active master.
> 
> (I use the collectd plugin and push data rather than poll, but the
> same principle should apply).
> 
> On 7 July 2015 at 14:02, Donald Laidlaw  wrote:
>> Has anyone ever developed Java code to detect the mesos masters and leader, 
>> given a zookeeper connection?
>> 
>> The reason I ask is because I would like to monitor mesos to report various 
>> metrics reported by the master. This requires detecting and tracking the 
>> leading master to query its /metrics/snapshot REST endpoint.
>> 
>> Thanks,
>> -Don

Re: Multi-mastersD

[Marco Massenzio]

(I'm sure I'm missing something here, so please forgive if I'm stating the
obvious)

This is actually very well supported right now: you can use "slave
attributes" (if, eg, you want to name the various clusters differently and
launch tasks according to those criteria) that would be passed on to the
Frameworks along with the resource offers: the frameworks could then decide
whether to accept the offer and launch tasks based on whatever logic you
want to implement.

You could use something like "--attributes="cluster:01z99; os:ubuntu-14-04;
jdk:8" or whatever makes sense.

*Marco Massenzio*
*Distributed Systems Engineer*

On Tue, Jul 7, 2015 at 8:55 AM, CCAAT  wrote:

> Hello team_mesos,
>
> Is there any reason one set of (3) masters cannot talk to and manage
> several (many) different slave clusters of (3)? These slave clusters
> would be different arch, different mixes of resources and be running
> different frameworks, but all share/use the same (3) masters.
>
>
> Ideas on how to architect this experiment, would be keenly appreciated.
>
>
> James
>
>

RE: Can marathon cancel a deployment if the application is "sick"?

[David Kesler]

I don't believe so.  We ran into a similar issue.  Investigation of marathon's 
github account revealed the following relevant tickets:

https://github.com/mesosphere/marathon/issues/1504
https://github.com/mesosphere/marathon/issues/
https://github.com/mesosphere/marathon/issues/1470


Basically, the issue is that as soon as the mesos task reaches the RUNNING 
state, marathon clears the exponential backoff, even if the task eventually 
fails.  Currently a ticket to fix it is slated for 0.10.0, but it's previously 
been slated for other releases and slipped.

(We actually set our deploy process up to create the new deployment and then 
periodically check on its status so that we can kill it if it times out so that 
we don't end up with perma-failing deployments in marathon.)


From: Maciej Strzelecki [mailto:maciej.strzele...@crealytics.com]
Sent: Tuesday, July 07, 2015 10:43 AM
To: user@mesos.apache.org
Subject: Can marathon cancel a deployment if the application is "sick"?


How to make marathon cancel a deployment if the app is not starting after 
several tries?

I saw those three settings (with defaults) in the documentation

"backoffSeconds": 1,

"backoffFactor": 1.15,

"maxLaunchDelaySeconds": 3600,

backoffSeconds, backoffFactor and maxLaunchDelaySeconds

Configures exponential backoff behavior when launching potentially sick apps. 
This prevents sandboxes associated with consecutively failing tasks from 
filling up the hard disk on Mesos slaves. The backoff period is multiplied by 
the factor for each consecutive failure until it reaches maxLaunchDelaySeconds. 
This applies also to tasks that are killed due to failing too many health 
checks.





I would expect to be able to tell marathon to "give up" after it tried few 
times. Is there a way?



backoffseconds - 5

factor -  high, -  100-200ish (so it reaches max delay very quickly after just 
a few failures)

maxdelay - 600 ( to allow for a docker pull to finish and general startup lag)



Root cause - a developer deploys application with either code failure - skipped 
test - or a docker image cant be pulled. If this task is left on 
marathon-retry-deployment for some time, mesos-ui shows thousands of failed 
tasks. Id love to see one, maybe two failed starts attempts, then "back-off".









Maciej Strzelecki
Operations Engineer
Tel: +49 30 6098381-50
Fax: +49 851-213728-88
E-mail: mstrzele...@crealytics.de
www.crealytics.com
blog.crealytics.com

crealytics GmbH - Semantic PPC Advertising Technology

Brunngasse 1 - 94032 Passau - Germany
Oranienstraße 185 - 10999 Berlin - Germany

Managing directors: Andreas Reiffen, Christof König, Dr. Markus Kurch
Register court: Amtsgericht Passau, HRB 7466
Geschäftsführer: Andreas Reiffen, Christof König, Daniel Trost
Reg.-Gericht: Amtsgericht Passau, HRB 7466

Multi-mastersD

[CCAAT]

Hello team_mesos,

Is there any reason one set of (3) masters cannot talk to and manage
several (many) different slave clusters of (3)? These slave clusters
would be different arch, different mixes of resources and be running
different frameworks, but all share/use the same (3) masters.


Ideas on how to architect this experiment, would be keenly appreciated.


James

Re: [VOTE] Release Apache Mesos 0.23.0 (rc1)

[CCAAT]

{++1} Non binding.

Gentoo works great on x64. Mostly working on arm8v.
Besides the more frequently release cycles keep the
work interesting and moving at a refreshing pace.
I.E. We've been on 0.22 too long..


hth,
James




On 07/06/2015 02:14 PM, Jörg Schad wrote:

After more testing:
-1 (non-binding)
Docker tests failing on CentOS Linux release 7.1.1503 (Core) , Tim is
already on the issue (see MESOS-2996)


On Mon, Jul 6, 2015 at 8:59 PM, Kapil Arya mailto:ka...@mesosphere.io>> wrote:

+1 (non-binding)

OpenSUSE Tumbleweed, Linux 4.0.3 / gcc 4.8.3

On Mon, Jul 6, 2015 at 2:33 PM, Ben Whitehead
mailto:ben.whiteh...@mesosphere.io>>
wrote:

+1 (non-binding)

openSUSE 13.2 Linux 3.16.7 / gcc-4.8.3
Tested running Marathon 0.9.0-RC3 and Cassandra on Mesos
0.1.1-SNAPSHOT.

On Mon, Jul 6, 2015 at 6:57 AM, Till Toenshoff mailto:toensh...@me.com>> wrote:

Even though Alex has IMHO already “busted” this vote ;) ..
THANKS ALEX! … ,
here are my results.

+1

OS 10.10.4 (14E46) + Apple LLVM version 6.1.0
(clang-602.0.53) (based on LLVM 3.6.0svn), make check -> OK
Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-32-generic x86_64)
+ gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2, make check -> OK





On Jul 6, 2015, at 3:22 PM, Alex Rukletsov
mailto:a...@mesosphere.com>> wrote:

-1

Compilation error on Mac OS 10.10.4 with clang 3.5, which
is supported according to release notes.
More details: https://issues.apache.org/jira/browse/MESOS-2991

On Mon, Jul 6, 2015 at 11:55 AM, Jörg Schad
mailto:jo...@mesosphere.io>> wrote:

P.S. to my prior +1
Tested on ubuntu-trusty-14.04 including docker.

On Sun, Jul 5, 2015 at 6:44 PM, Jörg Schad
mailto:jo...@mesosphere.io>> wrote:

+1

On Sun, Jul 5, 2015 at 4:36 PM, Nikolaos Ballas
neXus mailto:nikolaos.bal...@nexusgroup.com>> wrote:

+1



Sent from my Samsung device


 Original message 
From: tommy xiao mailto:xia...@gmail.com>>
Date: 05/07/2015 15:14 (GMT+01:00)
To: user@mesos.apache.org

Subject: Re: [VOTE] Release Apache Mesos
0.23.0 (rc1)

+1

2015-07-04 12:32 GMT+08:00 Weitao
mailto:zhouwtl...@gmail.com>>:

+1

发自我的 iPhone

在 2015年7月4日，09:41，Marco Massenzio
mailto:ma...@mesosphere.io>> 写道：


+1

/Marco Massenzio/
/Distributed Systems Engineer/

On Fri, Jul 3, 2015 at 12:25 PM, Adam
Bordelon mailto:a...@mesosphere.io>> wrote:

Hello Mesos community,

Please vote on releasing the
following candidate as Apache Mesos
0.23.0.

0.23.0 includes the following:


- Per-container network isolation
- Upgraded minimum required compilers
to GCC 4.8+ or clang 3.5+.
- Dockerized slaves will properly
recover Docker containers upon failover.

as well as experimental support for:
- Fetcher Caching
- Revocable Resources
- SSL encryption
- Persistent Volumes
- Dynamic Reservations

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.23.0-rc1



The candidate for Mesos 0.23.0
release is available at:

https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc1/mesos-0.23.0.tar.gz

The tag to be voted on is 0.23.0-rc1:

ht

Re: Java detector for mess masters and leader

[Marco Massenzio]

Hi Donald,

the information stored in the Zookeeper znode is a serialized Protocol
Buffer (see MasterInfo in mesos/mesos.proto
);
here is a brief explanation of what is in there, plus an example as to how
to retrieve that info (in Python - but Java would work pretty much the
same):
http://codetrips.com/2015/06/12/apache-mesos-leader-master-discovery-using-zookeeper/

Please be aware that, as of 0.24 (currently planned for mid-August), we
plan to publish that information *only* in JSON (exactly to help all the
folks like you) so the method presented there will no longer work (for all
intents and purposes, the serialized MasterInfo to ZK is considered
"deprecated" as of 0.23 which is going out any day now: we're currently
testing a RC).

Note that if you intend to "follow" the leader you will need to set a
"Watcher" on the node itself or, perhaps better, on the znode path, so as
to get a callback whenever anything changes: the elected leader will always
be the lowest-numbered ephemeral znode (I am guessing you know all this,
but feel free to ping me if you need more info).

Hope this helps.


*Marco Massenzio*
*Distributed Systems Engineer*

On Tue, Jul 7, 2015 at 6:02 AM, Donald Laidlaw  wrote:

> Has anyone ever developed Java code to detect the mesos masters and
> leader, given a zookeeper connection?
>
> The reason I ask is because I would like to monitor mesos to report
> various metrics reported by the master. This requires detecting and
> tracking the leading master to query its /metrics/snapshot REST endpoint.
>
> Thanks,
> -Don

Can marathon cancel a deployment if the application is "sick"?

[Maciej Strzelecki]

How to make marathon cancel a deployment if the app is not starting after 
several tries?

I saw those three settings (with defaults) in the documentation

"backoffSeconds": 1,
"backoffFactor": 1.15,
"maxLaunchDelaySeconds": 3600,

backoffSeconds, backoffFactor and maxLaunchDelaySeconds

Configures exponential backoff behavior when launching potentially sick apps. 
This prevents sandboxes associated with consecutively failing tasks from 
filling up the hard disk on Mesos slaves. The backoff period is multiplied by 
the factor for each consecutive failure until it reaches maxLaunchDelaySeconds. 
This applies also to tasks that are killed due to failing too many health 
checks.



I would expect to be able to tell marathon to "give up" after it tried few 
times. Is there a way?


backoffseconds - 5

factor -  high, -  100-200ish (so it reaches max delay very quickly after just 
a few failures)

maxdelay - 600 ( to allow for a docker pull to finish and general startup lag)


Root cause - a developer deploys application with either code failure - skipped 
test - or a docker image cant be pulled. If this task is left on 
marathon-retry-deployment for some time, mesos-ui shows thousands of failed 
tasks. Id love to see one, maybe two failed starts attempts, then "back-off".





Maciej Strzelecki
Operations Engineer
Tel: +49 30 6098381-50
Fax: +49 851-213728-88
E-mail: mstrzele...@crealytics.de
www.crealytics.com
blog.crealytics.com

crealytics GmbH - Semantic PPC Advertising Technology

Brunngasse 1 - 94032 Passau - Germany
Oranienstraße 185 - 10999 Berlin - Germany

Managing directors: Andreas Reiffen, Christof König, Dr. Markus Kurch
Register court: Amtsgericht Passau, HRB 7466
Geschäftsführer: Andreas Reiffen, Christof König, Daniel Trost
Reg.-Gericht: Amtsgericht Passau, HRB 7466

mesos-execute + docker_image

[Jürgen Jakobitsch]

hi,

i just installed mesos-0.22.0 (from the mesossphere repos) on centOS6.
can anyone point me into the right direction on how to run a docker image
inside mesos using mesos-execute plus the docker_image parameter.

also note that i would like to pass some parameters to the docker run
command

any pointer really appreciated.

wkr j


| Jürgen Jakobitsch,
| Software Developer
| Semantic Web Company GmbH
| Mariahilfer Straße 70 / Neubaugasse 1, Top 8
| A - 1070 Wien, Austria
| Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22

COMPANY INFORMATION
| web   : http://www.semantic-web.at/
| foaf  : http://company.semantic-web.at/person/juergen_jakobitsch
PERSONAL INFORMATION
| web   : http://www.turnguard.com
| foaf  : http://www.turnguard.com/turnguard
| g+: https://plus.google.com/111233759991616358206/posts
| skype : jakobitsch-punkt
| xmlns:tg  = "http://www.turnguard.com/turnguard#";

Re: Java detector for mess masters and leader

[Dick Davies]

The active master has a flag set in  /metrics/snapshot  :
"master/elected" which is 1 for the active
master and 0 otherwise, so it's easy enough to only load the metrics
from the active master.

(I use the collectd plugin and push data rather than poll, but the
same principle should apply).

On 7 July 2015 at 14:02, Donald Laidlaw  wrote:
> Has anyone ever developed Java code to detect the mesos masters and leader, 
> given a zookeeper connection?
>
> The reason I ask is because I would like to monitor mesos to report various 
> metrics reported by the master. This requires detecting and tracking the 
> leading master to query its /metrics/snapshot REST endpoint.
>
> Thanks,
> -Don

Re: Java detector for mess masters and leader

[Nikolaos Ballas neXus]

The only downside to that approach is that you consider you have apriori 
knowledge of the ip’s of the master. But if you are doing that from an external 
application and the nodes goes up and down the same ip/master/state.json can’t 
be conceived as granted. I used to go down that path, but if you want more 
dynamic behaviour extracting this way the leader in my mind makes more sense. 
Still proposal 100% functional and working :) worked like that for several 
weeks :D

Nikolaos Ballas  |  Software Development Manager

Technology Nexus S.a.r.l.
2-4 Rue Eugene Rupert
2453 Luxembourg
Delivery address: 2-3 Rue Eugene Rupert,Vertigo Polaris Building
Tel: + 3522619113580
cont...@nexusgroup.com | 
nexusgroup.com
LinkedIn.com | 
Twitter | 
Facebook.com


[cid:19B646FC-B8E7-4F77-BBD3-75DD7B4B5BF7]

On 07 Jul 2015, at 15:20, Philippe Laflamme 
mailto:phili...@hopper.com>> wrote:

Querying for /master/state.json will provide you with the master. So you can 
query any one of the hosts in your list of potential masters, extract the 
master information from that and then hit your master on the endpoint you're 
interested in.

Philippe

On Tue, Jul 7, 2015 at 9:02 AM, Donald Laidlaw 
mailto:donlaid...@me.com>> wrote:
Has anyone ever developed Java code to detect the mesos masters and leader, 
given a zookeeper connection?

The reason I ask is because I would like to monitor mesos to report various 
metrics reported by the master. This requires detecting and tracking the 
leading master to query its /metrics/snapshot REST endpoint.

Thanks,
-Don

Re: Java detector for mess masters and leader

[Philippe Laflamme]

Querying for /master/state.json will provide you with the master. So you
can query any one of the hosts in your list of potential masters, extract
the master information from that and then hit your master on the endpoint
you're interested in.

Philippe

On Tue, Jul 7, 2015 at 9:02 AM, Donald Laidlaw  wrote:

> Has anyone ever developed Java code to detect the mesos masters and
> leader, given a zookeeper connection?
>
> The reason I ask is because I would like to monitor mesos to report
> various metrics reported by the master. This requires detecting and
> tracking the leading master to query its /metrics/snapshot REST endpoint.
>
> Thanks,
> -Don

Re: Java detector for mess masters and leader

[Nikolaos Ballas neXus]

Just not to forget,
you can use the native Zookeeper API but in that case you should be aware that 
detecting the leader is a bit tricky. You ask for getPath(“/mesos/“ , true) and 
then you iterate over the children again calling getPath(). The string object 
returned contains some timestamps and a string mesos@ip:5050*ip … this will 
return you the masters but not the leader. In order to discover the leader you 
should use the number after the first - on the string you will see(timestamp) 
and the smaller number is actually the leader.If I have understood correctly. 
You can check the equivalent code in apache mesos where this prefix is added in 
case the request for registration in the zookeeper takes place.Again it looks 
for string index of (mesos@).

kind regards
Nikolaos Ballas  |  Software Development Manager

Technology Nexus S.a.r.l.
2-4 Rue Eugene Rupert
2453 Luxembourg
Delivery address: 2-3 Rue Eugene Rupert,Vertigo Polaris Building
Tel: + 3522619113580
cont...@nexusgroup.com | 
nexusgroup.com
LinkedIn.com | 
Twitter | 
Facebook.com


[cid:19B646FC-B8E7-4F77-BBD3-75DD7B4B5BF7]

On 07 Jul 2015, at 15:02, Donald Laidlaw 
mailto:donlaid...@me.com>> wrote:

Has anyone ever developed Java code to detect the mesos masters and leader, 
given a zookeeper connection?

The reason I ask is because I would like to monitor mesos to report various 
metrics reported by the master. This requires detecting and tracking the 
leading master to query its /metrics/snapshot REST endpoint.

Thanks,
-Don

Re: Java detector for mess masters and leader

[David Greenberg]

You can check out Satellite: https://github.com/twosigma/satellite which is
a complete monitoring & metrics system for Mesos. It avoids the need to
snoop the ZK connection by instead discovering that info via the rest API.

On Tue, Jul 7, 2015 at 9:03 AM Donald Laidlaw  wrote:

> Has anyone ever developed Java code to detect the mesos masters and
> leader, given a zookeeper connection?
>
> The reason I ask is because I would like to monitor mesos to report
> various metrics reported by the master. This requires detecting and
> tracking the leading master to query its /metrics/snapshot REST endpoint.
>
> Thanks,
> -Don

Re: Java detector for mess masters and leader

[Nikolaos Ballas neXus]

Hi Don,
actually you can use Apache Curator, to create a connection to Zookeeper and 
then instantiate a LeaderSelector object. If you pass as path the path under 
which you mesos master nodes register for formaming an ensemble then the that 
object you can call getLeader() or getParticipants and that is a json object 
that has an attribute calls isLeader. The participant that has this set to true 
is the leader. To receive that for Marathon you must search for 
/marathon/leader again with the same notion. Also take into consideration with 
LeaderSelector you can be notified for changes of the cluster topology(failure 
of the leader and re election).

http://curator.apache.org

http://curator.apache.org/apidocs/index.html

hope it’s clear.

kind regards
Nikolaos Ballas  |  Software Development Manager

Technology Nexus S.a.r.l.
2-4 Rue Eugene Rupert
2453 Luxembourg
Delivery address: 2-3 Rue Eugene Rupert,Vertigo Polaris Building
Tel: + 3522619113580
cont...@nexusgroup.com | 
nexusgroup.com
LinkedIn.com | 
Twitter | 
Facebook.com


[cid:19B646FC-B8E7-4F77-BBD3-75DD7B4B5BF7]

On 07 Jul 2015, at 15:02, Donald Laidlaw 
mailto:donlaid...@me.com>> wrote:

Has anyone ever developed Java code to detect the mesos masters and leader, 
given a zookeeper connection?

The reason I ask is because I would like to monitor mesos to report various 
metrics reported by the master. This requires detecting and tracking the 
leading master to query its /metrics/snapshot REST endpoint.

Thanks,
-Don

Java detector for mess masters and leader

[Donald Laidlaw]

Has anyone ever developed Java code to detect the mesos masters and leader, 
given a zookeeper connection?

The reason I ask is because I would like to monitor mesos to report various 
metrics reported by the master. This requires detecting and tracking the 
leading master to query its /metrics/snapshot REST endpoint.

Thanks,
-Don

RE: Lots of master elections

[Ashic Mahtab]

Ah..that was while I was setting things up. I guess if one master goes 
down, I'm temporarily in that scenario, hence I'd expect it to work - 
which it does. I think the issue was that the apt-get install started the 
service, and I changed settings, and it needed a clearing up of the cached 
information.

Date: Tue, 7 Jul 2015 10:33:20 +0200
Subject: Re: Lots of master elections
From: a...@mesosphere.com
To: user@mesos.apache.org

Got it. I was confused by your first email where you said you have 2 masters.
On Tue, Jul 7, 2015 at 4:40 AM, Ashic Mahtab  wrote:



Sure, Alex.
3 masters. Quorum is 2.

Date: Mon, 6 Jul 2015 19:44:28 +0200
Subject: Re: Lots of master elections
From: a...@mesosphere.com
To: user@mesos.apache.org

Ashic,
great that you solved the issue. Could you please clarify what HA configuration 
you have: how many masters and what --quorum you use?
On Sat, Jul 4, 2015 at 5:09 PM, Ashic Mahtab  wrote:



Hi Nikolaos,I'm using an external zk, so didn't need to restart it. 
I might have jumped the gun slightly in the last email. It seems completely 
omitting hostname in /etc/default/mesos-master is fine. Simply having a file 
called hostname in /etc/mesos-master with the desired hostname as the content 
seems to fix it for the web UI redirects. I had the file on the host I was 
setting up scripts with, but forgot to add that step for the others, hence the 
private ip redirects.
So, to summarise, I did the following:* Stopped mesos masters.* cleared 
/var/lib/mesos/** for each node, added /etc/mesos-master/hostname with the 
content of the file being the fully qualified hostname.* deleted the /mesos 
node in zk (though I don't know if this is necessary).* restarted each node.
Again, your guidance has helped greatly.
Cheers,Ashic.

From: nikolaos.bal...@nexusgroup.com
To: user@mesos.apache.org
Subject: Re: Lots of master elections
Date: Sat, 4 Jul 2015 14:25:27 +






Hi,
in my case, in order to make it work, I do the following:
1)stop zookeeper - mesos 
2)clean /var/lib/mesos/* /var/lib/zookeeper/version-X
3)restart zookeeper nodes
4)restart all mesos masters


















Nikolaos Ballas 
 |  Software Development Manager 







Technology Nexus S.a.r.l.

2-4 Rue Eugene Rupert

2453 Luxembourg

Delivery address: 2-3 Rue Eugene Rupert,Vertigo Polaris Building

Tel: + 3522619113580

cont...@nexusgroup.com | nexusgroup.com 

LinkedIn.com | Twitter | Facebook.com


















On 04 Jul 2015, at 15:04, Ashic Mahtab  wrote:




Hm...will delete everything in /var/lib/mesos (which are replicated logs), and 
retry. Guess I don't need to delete mesos things under /etc, then. Will report 
back. Checking the logs, I see that a master is elected but then writes this to 
FATAL:



F0704 12:52:38.078475  5847 master.cpp:1176] Recovery failed: Failed to recover 
registrar: Failed to perform fetch within 1mins



Then dies. Guess that's kicking off the new election.



-Ashic.





From: nikolaos.bal...@nexusgroup.com

To: user@mesos.apache.org

Subject: RE: Lots of master elections

Date: Sat, 4 Jul 2015 12:47:53 +



Based on your configuration under /var/  mesos creates  files. Under the 
directory mesos. Go inside var and run on command line find . - name *mesos* 










Sent from my Samsung device





 Original message 

From: Ashic Mahtab  

Date: 04/07/2015 14:34 (GMT+01:00) 

To: Apache Mesos  

Subject: RE: Lots of master elections 




Thanks for the reply, Niklaos. Extrme noob question...when you say mesos files, 
which are you referring to? Would I also need to delete the /mesos value in 
Zookeeper?





From: nikolaos.bal...@nexusgroup.com

To: user@mesos.apache.org

Subject: RE: Lots of master elections

Date: Sat, 4 Jul 2015 12:29:44 +



You have to  clean the mesos files and restart the masters 










Sent from my Samsung device





 Original message 

From: Ashic Mahtab  

Date: 04/07/2015 14:08 (GMT+01:00) 

To: user@mesos.apache.org 

Subject: Lots of master elections 




Hello,
Just getting started with Mesos, and in the process of "graduating" from 
Vagrant to a cluster on Azure. Here's what I have:



* 1 Zookeeper node exposing 2181, running as expected.
* 2 Mesos masters - mesos1.x.net,
mesos2.x.net. Both exposing 5050. These have private and public ips. All nodes 
are on the same network, and have access to each other.



[I'll set up a third master, and add slaves soon.]



It all seems ok, and the web UI works. I can see mesos entries in Zookeeper. 
However, I've seeing a couple of things:



* A node is elected master. And about a minute later, another election is held. 
(say,
mesos1.x.net)
* If the other node wins, in the UI, I get the message that this is no longer 
the master and am redirected.
* Sometimes the redirection is to 
mesos2.x.net, and all is fine (except another election soon). 
* Sometimes the redirection is to the internal ip of 
mesos2.x.net, which obviously gets a 404.



I should add that all the n

Re: Lots of master elections

[Alex Rukletsov]

Got it. I was confused by your first email where you said you have 2
masters.

On Tue, Jul 7, 2015 at 4:40 AM, Ashic Mahtab  wrote:

> Sure, Alex.
>
> 3 masters. Quorum is 2.
>
> --
> Date: Mon, 6 Jul 2015 19:44:28 +0200
> Subject: Re: Lots of master elections
> From: a...@mesosphere.com
> To: user@mesos.apache.org
>
>
> Ashic,
>
> great that you solved the issue. Could you please clarify what HA
> configuration you have: how many masters and what --quorum you use?
>
> On Sat, Jul 4, 2015 at 5:09 PM, Ashic Mahtab  wrote:
>
> Hi Nikolaos,
> I'm using an external zk, so didn't need to restart it.
>
> I might have jumped the gun slightly in the last email. It seems
> completely omitting hostname in /etc/default/mesos-master is fine. Simply
> having a file called hostname in /etc/mesos-master with the desired
> hostname as the content seems to fix it for the web UI redirects. I had the
> file on the host I was setting up scripts with, but forgot to add that step
> for the others, hence the private ip redirects.
>
> So, to summarise, I did the following:
> * Stopped mesos masters.
> * cleared /var/lib/mesos/*
> * for each node, added /etc/mesos-master/hostname with the content of the
> file being the fully qualified hostname.
> * deleted the /mesos node in zk (though I don't know if this is necessary).
> * restarted each node.
>
> Again, your guidance has helped greatly.
>
> Cheers,
> Ashic.
>
> --
> From: nikolaos.bal...@nexusgroup.com
> To: user@mesos.apache.org
> Subject: Re: Lots of master elections
> Date: Sat, 4 Jul 2015 14:25:27 +
>
>
> Hi,
> in my case, in order to make it work, I do the following:
> 1)stop zookeeper - mesos
> 2)clean /var/lib/mesos/* /var/lib/zookeeper/version-X
> 3)restart zookeeper nodes
> 4)restart all mesos masters
>
>
>*Nikolaos Ballas*  |  Software Development Manager
>
>  Technology Nexus S.a.r.l.
>  2-4 Rue Eugene Rupert
>  2453 Luxembourg
>  Delivery address: 2-3 Rue Eugene Rupert,Vertigo Polaris Building
>  Tel: + 3522619113580
>  cont...@nexusgroup.com  | nexusgroup.com
> 
>  *LinkedIn.com * | *Twitter
> * | *Facebook.com
> *
>
>
>
>  On 04 Jul 2015, at 15:04, Ashic Mahtab  wrote:
>
>  Hm...will delete everything in /var/lib/mesos (which are replicated
> logs), and retry. Guess I don't need to delete mesos things under /etc,
> then. Will report back. Checking the logs, I see that a master is elected
> but then writes this to FATAL:
>
>  F0704 12:52:38.078475  5847 master.cpp:1176] Recovery failed: Failed to
> recover registrar: Failed to perform fetch within 1mins
>
>  Then dies. Guess that's kicking off the new election.
>
>  -Ashic.
>
>  --
> From: nikolaos.bal...@nexusgroup.com
> To: user@mesos.apache.org
> Subject: RE: Lots of master elections
> Date: Sat, 4 Jul 2015 12:47:53 +
>
> Based on your configuration under /var/  mesos creates  files. Under the
> directory mesos. Go inside var and run on command line find . - name
> *mesos*
>
>
>
>  Sent from my Samsung device
>
>
>  Original message 
> From: Ashic Mahtab 
> Date: 04/07/2015 14:34 (GMT+01:00)
> To: Apache Mesos 
> Subject: RE: Lots of master elections
>
>  Thanks for the reply, Niklaos. Extrme noob question...when you say mesos
> files, which are you referring to? Would I also need to delete the /mesos
> value in Zookeeper?
>
>  --
> From: nikolaos.bal...@nexusgroup.com
> To: user@mesos.apache.org
> Subject: RE: Lots of master elections
> Date: Sat, 4 Jul 2015 12:29:44 +
>
> You have to  clean the mesos files and restart the masters
>
>
>
>  Sent from my Samsung device
>
>
>  Original message 
> From: Ashic Mahtab 
> Date: 04/07/2015 14:08 (GMT+01:00)
> To: user@mesos.apache.org
> Subject: Lots of master elections
>
>  Hello,
> Just getting started with Mesos, and in the process of "graduating" from
> Vagrant to a cluster on Azure. Here's what I have:
>
>  * 1 Zookeeper node exposing 2181, running as expected.
> * 2 Mesos masters - mesos1.x.net, mesos2.x.net. Both exposing 5050. These
> have private and public ips. All nodes are on the same network, and have
> access to each other.
>
>  [I'll set up a third master, and add slaves soon.]
>
>  It all seems ok, and the web UI works. I can see mesos entries in
> Zookeeper. However, I've seeing a couple of things:
>
>  * A node is elected master. And about a minute later, another election
> is held. (say, mesos1.x.net)
> * If the other node wins, in the UI, I get the message that this is no
> longer the master and am redirected.
> * Sometimes the redirection is to mesos2.x.net, and all is fine (except
> another election soon).
> * Sometimes the redirection is to the internal ip of mesos2.x.net, which
> obviously gets a 404.
>

Re: about adding new slave

[Rik]

CPU shares have a bit a dual role. see:
http://theza.ch/2014/09/17/cpu-resources-in-docker-mesos-and-marathon/

In short: essentially yes, it would be the same share, but it's not
limited to that at all times.

On Tue, Jul 7, 2015 at 7:06 AM, Badal Naik  wrote:
> Hello There , I have a question. i have started mesos cluser 3 master-3
> slave i have started some instances with specific cpu shares now if i add a
> new server machine as slave with more cpu should i get the same cpu share?