Hi,
I'm trying to do a clean build of mesos for the 0.19.0 tarball.
I was following the instructions from
http://mesos.apache.org/gettingstarted/ step by step. Got to running
`make`, which ran for quite a while, and exited with errors (see the end of
the output below).
Extra env info: I'm trying
Hi,
that's quite strange. Try to run
ldconfig
and then again make.
You can find binary packages for Debian here:
http://mesosphere.io/downloads/
Tomas
On 23 July 2014 10:09, Itamar Ostricher wrote:
> Hi,
>
> I'm trying to do a clean build of mesos for the 0.19.0 tarball.
> I was following t
Thanks Tomas.
ldconfig didn't change anything. make still failed.
But the Debian packaged installed like a charm, so I'm good :-)
Now I just need to figure out how to use it...
(going to start with [1], unless anyone chimes in with a better recommended
starting point for a mesos-newbie who is try
Define many :) If you want to use some provisioning tools like Puppet,
Chef, Ansible... there are quite a few modules to do this job:
http://mesosphere.io/learn/#tools
If you have only a few machines, you might be fine with deploy scripts.
An example of MPI framework is here:
https://github.com
23, 2014 5:26:25 AM
> Subject: Re: mesos build errors
> Thanks Tomas.
> ldconfig didn't change anything. make still failed.
> But the Debian packaged installed like a charm, so I'm good :-)
> Now I just need to figure out how to use it...
> (going to start with [1], un
many: we have a processing pipeline with ~10 stages (one C++ program per
stage usually), batch processing (almost-)all pairs of files in the
dataset. the dataset contains >10K files at the moment, so a couple of
hundreds of millions of program executions would be my definition for
"many" in this ca
Depends on the nature of your tasks. Your code is written in MPI? You tasks
needs to communicate with others? One task will operate on all files, some
subset, or just on file? You might have:
- one task per machine running on as many cores as possible
- many smaller tasks starting in a dy
Not written in MPI. Each task is a stand-alone execution of a binary
program that takes the 1-2 data file paths as parameters (GCS paths), with
the output stored in another GCS file (path as flag).
Different tasks do not need to communicate with others. Tasks only talk
with GCS to read and write th
For scheduling workflows of batch jobs, I would recommend looking into the
Chronos framework for Mesos:
https://github.com/airbnb/chronos
http://mesosphere.io/learn/run-chronos-on-mesos/
http://nerds.airbnb.com/introducing-chronos/
On Thu, Jul 24, 2014 at 4:58 AM, Itamar Ostricher
wrote:
> Not
Thanks for the tip Adam.
We briefly looked at Chronos a couple of days ago, and felt like it was an
overkill for us.
Just yesterday we were able to successfully distribute part of our workload
across a 15-node mesos cluster (240 cores) using a modified mesos-submit
framework we hacked from the exa
chronos looks interesting, but we have tasks we need to do regularly that
are part of a rails project. currently we are running it using sidekiq
workers + clock using docker via marathon.
how would I be able to run it on Chronos as I cant see any special way of
running a task within a docker conta
Hi Nayeem,
You could use Deimos to set a default Docker image to push your tasks into,
but Chronos currently lacks the configuration interface necessary to run a
specific Docker container as a job.
It shouldn't be difficult to add, since the support is already there in
Mesos. I filed https://githu
12 matches
Mail list logo
