Re: Help interpreting output from running java test-framework example

Thanks, Stephen - feedback much appreciated! *Marco Massenzio* *Distributed Systems Engineerhttp://codetrips.com * On Thu, Sep 17, 2015 at 5:03 PM, Stephen Boesch wrote: > Compared to Yarn Mesos is just faster. Mesos has a smaller startup time > and

Re: Help interpreting output from running java test-framework example

As you know, Mesoscon Europe is fast approaching. At Mesoscon Europe, I'll be giving a talk on our advanced, preempting, multi-tenant spark on Mesos scheduler--Cook. Most excitingly, this framework will be fully open source by then! So, you might be able to switch to Mesos even sooner. If you're

Re: Help interpreting output from running java test-framework example

Hey Stephen, The spark on mesos is twice as fast as yarn on our 20 node cluster. In > addition Mesos is handling datasizes that yarn simply dies on it. But > mesos is still just taking linearly increased time compared to smaller > datasizes. Obviously delighted to hear that, BUT me not much

Re: Help interpreting output from running java test-framework example

Compared to Yarn Mesos is just faster. Mesos has a smaller startup time and the delay between tasks is smaller. The run times for terasort 100GB tended towards 110sec median on Mesos vs about double that on Yarn. Unfortunately we require mature Multi-Tenancy/Isolation/Queues support -which is

Re: Help interpreting output from running java test-framework example

Thanks Vinod. I went back to see the logs and nothing interesting . However int he process I found that my spark port was pointing to 7077 instead of 5050. After re-running .. spark on mesos worked! The spark on mesos is twice as fast as yarn on our 20 node cluster. In addition Mesos is handling

Re: Help interpreting output from running java test-framework example

sounds like it. can you see what the slave/agent and executor logs say? On Tue, Sep 8, 2015 at 11:46 AM, Stephen Boesch wrote: > > I am in the process of learning how to run a mesos cluster with the intent > for it to be the resource manager for Spark. As a small step in

Help interpreting output from running java test-framework example

I am in the process of learning how to run a mesos cluster with the intent for it to be the resource manager for Spark. As a small step in that direction a basic test of mesos was performed, as suggested by the Mesos Getting Started page. In the following output we see tasks launched and