Paco, that's a great video reference, thanks. To be fair to our friends at Yahoo, who have done a tremendous amount to help advance the cause of the BDAS stack, it's not FUD coming from them, certainly not in any organized or intentional manner.
In vacuo we prefer Mesos ourselves, but also can't ignore the fact that in the larger market, many enterprise technology stack decisions are made based on their existing vendor support relationships. And in view of Mesos, super happy to see Mesosphere growing! Sent while mobile. Pls excuse typos etc. That's FUD. Tracking the Mesos and Spark use cases, there are very large production deployments of these together. Some are rather private but others are being surfaced. IMHO, one of the most amazing case studies is from Christina Delimitrou http://youtu.be/YpmElyi94AA For a tutorial, use the following but upgrade it to latest production for Spark. There was a related O'Reilly webcast and Strata tutorial as well: http://mesosphere.io/learn/run-spark-on-mesos/ FWIW, I teach "Intro to Spark" with sections on CM4, YARN, Mesos, etc. Based on lots of student experiences, Mesos is clearly the shortest path to deploying a Spark cluster if you want to leverage the robustness, multi-tenancy for mixed workloads, less ops overhead, etc., that show up repeatedly in the use case analyses. My opinion only and not that of any of my clients: "Don't believe the FUD from YHOO unless you really want to be stuck in 2009." On Wed, May 7, 2014 at 8:30 AM, deric <barton.to...@gmail.com> wrote: > I'm also using right now SPARK_EXECUTOR_URI, though I would prefer > distributing Spark as a binary package. > > For running examples with `./bin/run-example ...` it works fine, however > tasks from spark-shell are getting lost. > > Error: Could not find or load main class > org.apache.spark.executor.MesosExecutorBackend > > which looks more like problem with sbin/spark-executor and missing paths to > jar. Anyone encountered this error before? > > I guess Yahoo invested quite a lot of effort into YARN and Spark > integration > (moreover when Mahout is migrating to Spark there's much more interest in > Hadoop and Spark integration). If there would be some "Mesos company" > working on Spark - Mesos integration it could be at least on the same > level. > > I don't see any other reason why would be YARN better than Mesos, > personally > I like the latter, however I haven't checked YARN for a while, maybe > they've > made a significant progress. I think Mesos is more universal and flexible > than YARN. > > > > -- > View this message in context: > http://apache-spark-user-list.1001560.n3.nabble.com/is-Mesos-falling-out-of-favor-tp5444p5481.html > Sent from the Apache Spark User List mailing list archive at Nabble.com. >
