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

Maybe also https://issues.apache.org/jira/browse/MESOS-4877 and https://issues.apache.org/jira/browse/MESOS-4878 ? On Tue, Mar 8, 2016 at 9:13 AM, Jie Yu wrote: > I'd like to fix https://issues.apache.org/jira/browse/MESOS-4888 as well > if you guys plan to cut another RC > > On Mon, Mar 7, 2016

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

Hi all, The vote for Mesos 0.27.2 (rc1) has passed with the following votes. +1 (Binding) -- Kapil Arya Vinod Kone Joris Van Remoortere +1 (Non-binding) -- Greg Mann Michael Browning There was one -1 non-binding vote from Kevin Klues. I fo

Re: Re: Mesos 0.25 not incresing Staged/Started counters in the UI

Non-terminal states are gauges (instantaneous measurements) whereas the terminal states are counters (always increasing, at least for the lifetime of a master process). Hopefully this image doesn't get stripped, but we improved the wording here to clarify which are gauges and which are counters:

Re: mesos agent not recovering after ZK init failure

Sure, will do. On Mon, Mar 7, 2016 at 5:54 PM, Benjamin Mahler wrote: > Very surprising.. I don't have any ideas other than trying to replicate > the scenario in a test. > > Please do keep us posted if you encounter it again and gain more > information. > > On Fri, Feb 26, 2016 at 4:34 PM, Shar

Re: mesos agent not recovering after ZK init failure

Very surprising.. I don't have any ideas other than trying to replicate the scenario in a test. Please do keep us posted if you encounter it again and gain more information. On Fri, Feb 26, 2016 at 4:34 PM, Sharma Podila wrote: > MESOS-4795 created. > > I don't have the exit status. We haven't

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

I'd like to fix https://issues.apache.org/jira/browse/MESOS-4888 as well if you guys plan to cut another RC On Mon, Mar 7, 2016 at 10:16 AM, Daniel Osborne < daniel.osbo...@metaswitch.com> wrote: > -1 > > If it doesn’t cause too much pain, I'm hoping we can squeeze a relatively > small patch whic

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

+1 (non-binding) `make check` and `sudo make check` on OSX 10.10.5 and CentOS 7.1, with libevent and SSL enabled. All tests pass on CentOS 7.1 When running the sudo tests on OSX, three failures were observed: ExamplesTest.JavaFramework is tracked by https://issues.apache.org/jira/browse/MESOS-35

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

Looks like there is a bunch of discussion around MESOS-4370 and RB# 43093. Kapil, as the shepherd, what is your take on the priority and readiness of this? On Mon, Mar 7, 2016 at 1:16 PM, Daniel Osborne < daniel.osbo...@metaswitch.com> wrote: > -1 > > If it doesn’t cause too much pain, I'm hoping

RE: [VOTE] Release Apache Mesos 0.28.0 (rc1)

-1 If it doesn’t cause too much pain, I'm hoping we can squeeze a relatively small patch which restores Mesos' ability to extract Docker assigned IPs. This has been broken with Docker 1.10's release over a month ago, and prevents service discovery and DNS from working. Mesos-4370: https://iss

Marathon SSLHandshakeException

Hi all, I am playing with SSL in Marathon 0.10 and Mesos 0.25. I could enable SSL in Marathon, creating a self-signed certificate and importing it into a java keystore. I did that from one of the 3 machines where Marathon runs. After, i copied the jks file to the two other machines, and restart

RE: mesos master 0.27.1 needs g++ to execute ?

Thanks, I am upgrading from 0.25 directly to 0.27.1. If this is the was mesos is going (i.e. relink) then I’ll manage. I’ll look into lt-mesos-master Sent from Mail for Windows 10 From: haosdent Sent: Monday, March 7,

Re: mesos master 0.27.1 needs g++ to execute ?

If you use automake tools to build mesos, the `mesos-master` actually is a warpper of "build/src/.libs/lt-mesos-master". And in the `mesos-master.sh`, g++ is needed when relink. Not only 0.27.1, but also before 0.27.1, g++ is always needed when relink. You could trigger relink after remove "build/s

RE: mesos master 0.27.1 needs g++ to execute ?

I am not doing the standard rpm, but am building from source and following their directions for running the mesos master. Mesos 0.25 runs fine -non-docker and docker and doesn’t need g++ to run. I can also run mesos master 0.27.1 fine non-docker and docker; I just want to know why mesos maste