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

[Adam Bordelon]

+1 (binding)
Green DC/OS integration tests when bumping DC/OS 1.9.x to Mesos 1.2.2-rc1:
https://github.com/dcos/dcos/pull/1800

On Fri, Aug 4, 2017 at 7:05 PM, Kapil Arya  wrote:

> +1 Green build on internal CI.
>
> The RC packages are available at: http://open.mesosphere.
> com/downloads/mesos-rc/#apache-mesos-1.2.2-rc1
>
> The following docker images based on Ubuntu 16.04 are also available:
> * mesosphere/mesos:1.2.2-rc1
> * mesosphere/mesos-master:1.2.2-rc1
> * mesosphere/mesos-agent:1.2.2-rc1
>
> Kapil
>
> On Fri, Aug 4, 2017 at 8:12 PM, Adam Bordelon  wrote:
>
>> Hello Mesos community,
>>
>> Please vote on releasing the following candidate as Apache Mesos 1.2.2.
>>
>> 1.2.2 includes the following:
>> 
>> 
>>
>>   * [MESOS-5187] - The filesystem/linux isolator does not set the
>> permissions of the host_path.
>>   * [MESOS-7252] - Need to fix resource check in long-lived framework.
>>   * [MESOS-7540] - Add an agent flag for executor re-registration timeout.
>>   * [MESOS-7546] - WAIT_NESTED_CONTAINER sometimes returns 404.
>>   * [MESOS-7569] - Allow "old" executors with half-open connections to
>> be preserved during agent upgrade / restart.
>>   * [MESOS-7581] - Fix interference of external Boost installations
>> when using some unbundled dependencies.
>>   * [MESOS-7689] - Libprocess can crash on malformed request paths for
>> libprocess messages.
>>   * [MESOS-7690] - The agent can crash when an unknown executor tries
>> to register.
>>   * [MESOS-7703] - Mesos fails to exec a custom executor when no shell is
>> used.
>>   * [MESOS-7728] - Java HTTP adapter crashes JVM when leading master
>> disconnects.
>>   * [MESOS-7770] - Persistent volume might not be mounted if there is
>> a sandbox volume whose source is the same as the target of the
>> persistent volume.
>>   * [MESOS-] - Agent failed to recover due to mount namespace
>> leakage in Docker 1.12/1.13.
>>   * [MESOS-7796] - LIBPROCESS_IP isn't passed on to the fetcher.
>>   * [MESOS-7830] - Sandbox_path volume does not have ownership set
>> correctly.
>>
>> The CHANGELOG for the release is available at:
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_p
>> lain;f=CHANGELOG;hb=1.2.2-rc1
>> 
>> 
>>
>> The candidate for Mesos 1.2.2 release is available at:
>> https://dist.apache.org/repos/dist/dev/mesos/1.2.2-rc1/mesos-1.2.2.tar.gz
>>
>> The tag to be voted on is 1.2.2-rc1:
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.2.2-rc1
>>
>> The MD5 checksum of the tarball can be found at:
>> https://dist.apache.org/repos/dist/dev/mesos/1.2.2-rc1/mesos
>> -1.2.2.tar.gz.md5
>>
>> The signature of the tarball can be found at:
>> https://dist.apache.org/repos/dist/dev/mesos/1.2.2-rc1/mesos
>> -1.2.2.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-1202
>>
>> Please vote on releasing this package as Apache Mesos 1.2.2!
>>
>> The vote is open until at least Wed Aug 9 at 5pm PDT 2017 and passes if a
>> majority of at least 3 +1 PMC votes are cast.
>>
>> [ ] +1 Release this package as Apache Mesos 1.2.2
>> [ ] -1 Do not release this package because ...
>>
>> Thanks,
>> -Adam and Alexander-
>>
>
>

Re: Command Executor

[Benjamin Mahler]

You're free to write your own long lived executor that can process multiple
tasks. The built in executors self-terminate after running the tasks they
are launched with.

On Tue, Aug 8, 2017 at 2:36 AM, Oeg Bizz  wrote:

> It is used to notify some services that the agents are out there ready to
> process data.  The service takes into account who and how many are out
> there and some information from the HB to perform some sort of load
> balancing.  Without the HB the service does not know how many agents are
> out and tasking is assigned only when an offer is received, but that is not
> as effective as it should be if the service would know in advance about the
> cluster's load.  Thanks,
>
> Oscar
>
>
> On Monday, August 7, 2017, 11:13:10 AM EDT, James Peach 
> wrote:
>
>
>
> > On Aug 5, 2017, at 3:03 AM, Oeg Bizz  wrote:
> >
> > I have a framework that relies on information sent by a custom Java
> Command Executor; think of some sort of heartbeat.  I start getting
> hearbeats after I send a task to that mesos-slave, but never before that.
> That makes me assume that the CommandExecutor is not started until a task
> is submitted to be executed by that agent.  Is there a way to tell
> mesos-slave to start the ComandExecutor as soon as it starts running?
>
> Not AFAIK. Executors are always spawned in order to execute tasks. In your
> case, what is the heartbeat for, if there are no tasks on the agent?
>
>
> J
>

Re: Deprecating `--disable-zlib` in libprocess

[Jie Yu]

+1 on removing this flag.

On Tue, Aug 8, 2017 at 11:32 AM, Benjamin Mahler  wrote:

> Sorry, I think this was me, feel free to remove it from libprocess now that
> it's required.
>
> On Tue, Aug 8, 2017 at 10:57 AM, Chun-Hung Hsiao 
> wrote:
>
> > Hi all,
> >
> > In libprocess, we have an optional `--disable-zlib` flag, but it's
> > currently not used
> > for conditional compilation and we always use zlib in libprocess,
> > and there's a requirement check in Mesos to make sure that zlib exists.
> > Should this option be removed then?
> > Or is there anyone working on a system without zlib?
> >
> > Thanks for your opinions!
> > Chun-Hung
> >
>

Re: Deprecating `--disable-zlib` in libprocess

[Benjamin Mahler]

Sorry, I think this was me, feel free to remove it from libprocess now that
it's required.

On Tue, Aug 8, 2017 at 10:57 AM, Chun-Hung Hsiao 
wrote:

> Hi all,
>
> In libprocess, we have an optional `--disable-zlib` flag, but it's
> currently not used
> for conditional compilation and we always use zlib in libprocess,
> and there's a requirement check in Mesos to make sure that zlib exists.
> Should this option be removed then?
> Or is there anyone working on a system without zlib?
>
> Thanks for your opinions!
> Chun-Hung
>

Re: Deprecating `--disable-zlib` in libprocess

[James Peach]

> On Aug 8, 2017, at 10:57 AM, Chun-Hung Hsiao  wrote:
> 
> Hi all,
> 
> In libprocess, we have an optional `--disable-zlib` flag, but it's
> currently not used
> for conditional compilation and we always use zlib in libprocess,
> and there's a requirement check in Mesos to make sure that zlib exists.
> Should this option be removed then?

Yes.

> Or is there anyone working on a system without zlib?
> 
> Thanks for your opinions!
> Chun-Hung

Deprecating `--disable-zlib` in libprocess

[Chun-Hung Hsiao]

Hi all,

In libprocess, we have an optional `--disable-zlib` flag, but it's
currently not used
for conditional compilation and we always use zlib in libprocess,
and there's a requirement check in Mesos to make sure that zlib exists.
Should this option be removed then?
Or is there anyone working on a system without zlib?

Thanks for your opinions!
Chun-Hung

Re: Command Executor

[Oeg Bizz]

It is used to notify some services that the agents are out there ready to 
process data.  The service takes into account who and how many are out there 
and some information from the HB to perform some sort of load balancing.  
Without the HB the service does not know how many agents are out and tasking is 
assigned only when an offer is received, but that is not as effective as it 
should be if the service would know in advance about the cluster's load.  
Thanks,
Oscar

On Monday, August 7, 2017, 11:13:10 AM EDT, James Peach  
wrote:


> On Aug 5, 2017, at 3:03 AM, Oeg Bizz  wrote:
> 
> I have a framework that relies on information sent by a custom Java Command 
> Executor; think of some sort of heartbeat.  I start getting hearbeats after I 
> send a task to that mesos-slave, but never before that.  That makes me assume 
> that the CommandExecutor is not started until a task is submitted to be 
> executed by that agent.  Is there a way to tell mesos-slave to start the 
> ComandExecutor as soon as it starts running?

Not AFAIK. Executors are always spawned in order to execute tasks. In your 
case, what is the heartbeat for, if there are no tasks on the agent?

J