Just FW. ---------- Forwarded message ---------- From: Ted Dunning <[email protected]> Date: Fri, Jul 1, 2011 at 10:21 AM Subject: Re: Question about Mesos. To: [email protected]
Technically speaking, Mesos has a less expressive model for expressing resource requirements. The thesis of Mesos is that the negotiation between application and scheduler can make up for this missing information. Mesos was also first to "market", but Hadoop nextGen is catching up fast. The MR-279 has code that works, albeit with some issues in production use. From all reports, these issues are being resolved quickly as Yahoo's considerable QA resources come to bear. Politically speaking, Mesos has a nearly inactive mailing list which, to outward appearances, indicate a nearly inactive project. There is some evidence that considerable activity is occurring off-list, but this is a process bug in the Apache model since "if it doesn't happen on the list, it doesn't happen". On the other side, Hadoop nextGen has the Hadoop community pretty much behind it. Since HNG has the potential to breakdown some of the deadlocks that have plagued the Hadoop community release process, there is considerable enthusiasm for it. Combined, these factors make it much more likely that HNG will be the dominant force in the Hadoop world. That is, more likely in my own estimation. Others may differ. On Thu, Jun 30, 2011 at 5:16 PM, Edward J. Yoon <[email protected]>wrote: > Hi, > > I'm newbie, and wonder what's the main differences between Hadoop > nextGen and Mesos. > > Thanks. > -- > Best Regards, Edward J. Yoon > @eddieyoon > -- Best Regards, Edward J. Yoon @eddieyoon
