Re: Apache Aurora Graduation

Congratulations, definitely well deserved. Great product and excellent support from the team. On 19 Mar 2015 04:22, "Toby Weingartner" wrote: > Congrats everyone, very well deserved! :) > > On Wed, Mar 18, 2015 at 2:19 PM, Henry Saputra > wrote: > > > Congratulations! > > > > On Wed, Mar 18, 201

Re: Attempting to Push Aurora to ~11 requests/second

https://gist.github.com/ryanorr/b3736c03a9919f9b87dc Just a simple bash script. I run 10-15 of them in the background and it crashes usually in less than 30 mins as described. Thanks for looking into it. On Wed, Mar 18, 2015 at 7:19 PM, Bill Farner wrote: > I'm slightly doubtful that GC is the

Getting exit codes from Thermos

I'm sending a job to Aurora that consists of multiple processes. One of them fails, failing the job. I'd like to get the return code for the failed process. Going to the Thermos observer on the slave that runs the job tells me which process failed, but there's no return code specified either in th

Re: Attempting to Push Aurora to ~11 requests/second

I've been running 10 forks of your script against a scheduler in the vagrant environment for a little over an hour, and have not had luck at inducing a crash yet. Are you able to repro there? Can you post the full scheduler log file from a repro of this? -=Bill On Thu, Mar 19, 2015 at 4:33 AM,

Re: Attempting to Push Aurora to ~11 requests/second

Same here. A single fork ran for 4 hours and I stopped it after 20K tasks. Running 30 forks now for about an hour or so, no failure so far (though vagrant IO ops stalled to a crawl). On Thu, Mar 19, 2015 at 3:25 PM, Bill Farner wrote: > I've been running 10 forks of your script against a schedule

Jenkins build is back to normal : Aurora #948

See

Re: Apache Aurora Graduation

Congrats everyone!! The only negative to this is all my aurora mail rules and git remotes are going to break! Jay On Thu, Mar 19, 2015 at 2:29 AM, Larry Weya wrote: > Congratulations, definitely well deserved. Great product and excellent > support from the team. > On 19 Mar 2015 04:22, "Toby W

/etc/passwd in containers

One pain point that currently exists with Aurora/Mesos/Docker integration is that it requires making a choice between two bad options: 1) require that the aurora role exist in the docker image as a unix user 2) run everything as root by setting "USER root" in the Dockerfile and pass --nosetuid to