Right now we're currently targeting mesos 0.20.1. Are there any short to
mid-term plans on upgrading to 0.21.0 (or greater?) Any reasons not to?
Internally we've been on 0.21.0 for a month or so without any issues.
I agree with everything here. A big pain point from the docker integration
side was/is the observer, and rolling the observer functionality into the
executor would simplify things greatly.
On Sat, Jan 24, 2015 at 12:29 PM, Bill Farner wrote:
> +1, thanks for the braindump, Brian! This sounds g
I removed that class from the coverage blacklist (
config/legacy_untested_classes.txt) in my docker patch, however the tests
worked fine in my branch?
On Mon, Jan 26, 2015 at 3:57 PM, Bill Farner wrote:
> Funny, this did not trip for me locally on the branch, but i can now repro
> on master. Ta
org/r/30285/
>
> -=Bill
>
> On Mon, Jan 26, 2015 at 1:02 PM, Steve Niemitz
> wrote:
>
> > I removed that class from the coverage blacklist (
> > config/legacy_untested_classes.txt) in my docker patch, however the tests
> > worked fine in my branch?
> >
&g
I ran into it today too when I was running end to end tests.
On Tue, Jan 27, 2015 at 2:53 PM, Bill Farner wrote:
> Yes, i also bumped into https://issues.apache.org/jira/browse/AURORA-1060
> on one out of 3 attempts.
>
> I'm overall +0 at this point since i have not been able to successfully run
I just submitted a review request to fix them,
https://reviews.apache.org/r/30331/
On Tue, Jan 27, 2015 at 2:54 PM, Steve Niemitz wrote:
> I ran into it today too when I was running end to end tests.
>
> On Tue, Jan 27, 2015 at 2:53 PM, Bill Farner wrote:
>
>> Yes, i also
+1 from me. Downloaded, built, and ran tests.
On Wed, Jan 28, 2015 at 3:22 PM, Joshua Cohen
wrote:
> +1 md5 matches, signature is valid, java, python and end to end tests all
> pass.
>
> On Wed, Jan 28, 2015 at 11:18 AM, Zameer Manji wrote:
>
> > +1 Release this as Apache Aurora 0.7.0
> >
> >
+1 here, everything looks good. I ran some tests on my end as well.
On Mon, Feb 2, 2015 at 2:40 PM, Bill Farner wrote:
> +1
>
> Signature and checksums are good, test suite passes, end-to-end tests pass.
>
> -=Bill
>
> On Sat, Jan 31, 2015 at 7:52 PM, Maxim Khutornenko
> wrote:
>
> > All,
> >
While we don't rely on the stats, I do think that they are nice to have.
Mesos doesn't export stats down to the per-process level, so we lose some
resolution there.
That being said, currently we run about 1/2 our jobs in docker, which
doesn't have per-process stats in the observer right now, so we
Is there a reason you set zk_in_proc=true? Setting it tells the scheduler
to ignore the "real" ZK server and use an in-proc one instead.
-zk_in_proc=false
Launches an embedded zookeeper server for local testing causing
-zk_endpoints to be ignored if specified.
(com.twitter.common.zookeeper.guice.
I was planning on starting both mount and network mode support either next
week or the week after. (Probably network mode support first).
However, based on the feedback from Bill, I think I might start with his
suggestion in the ticket, and allow static mounts specified to the
scheduler. This wo
+1
On Wed, Feb 18, 2015 at 6:08 PM, Kevin Sweeney wrote:
> +1!
>
> On Wed, Feb 18, 2015 at 5:55 PM, Henry Saputra
> wrote:
>
> > +1
> >
> >
> > On Wednesday, February 18, 2015, Jake Farrell
> wrote:
> >
> > > Based on community discussions on the project mailing lists and the
> > current
> > >
Just adding our experience here:
We've never used the thermos CLI nor do we even install it on our slaves
(is that even where it's supposed to go?). The scheduler + observer +
mesos UI have been enough to troubleshoot 99% of the problems we've run
into.
On Mon, Feb 23, 2015 at 3:58 PM, Zameer Ma
Oh awesome, yeah I'm in. That's good timing because I'll be out in SF the
week after (the 30th).
On Mon, Mar 9, 2015 at 4:50 PM, Dave Lester wrote:
> Hi all,
>
> Later this week we'll be announcing a NYC Apache Aurora meetup that will
> take place the week of March 23rd, likely occurring on Wed
>From the mesos slave log it looks like the executor is failing. Most
likely the issue is your image doesn't have the native libraries needed to
run it. The next step would be to look in the sandbox for a failed run
(you can find the path in the slave logs) and look at the stderr log for
errors.
I just noticed this line in your previous email:
"Everything's included in the image, that's the image i'm running mesos-master,
aurora, and mesos-slave from."
Are you saying you're running the slave inside a docker container? If so,
mesos does not support running docker containers from inside an
16 matches
Mail list logo
